Virtual assistant activation

ABSTRACT

At an electronic device with a display, a microphone, and an input device: while the display is on, receiving user input via the input device, the user input meeting a predetermined condition; in accordance with receiving the user input meeting the predetermined condition, sampling audio input received via the microphone; determining whether the audio input comprises a spoken trigger; and in accordance with a determination that audio input comprises the spoken trigger, triggering a virtual assistant session.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/696,378, filed Nov. 26, 2019, entitled “VIRTUAL ASSISTANTACTIVATION,” which is a continuation of U.S. patent application Ser. No.15/862,286, filed Jan. 4, 2018, entitled “VIRTUAL ASSISTANT ACTIVATION,”which is a divisional of U.S. patent application Ser. No. 14/841,449,filed Aug. 31, 2015, entitled “VIRTUAL ASSISTANT ACTIVATION,” whichclaims the benefit of priority of U.S. Provisional Patent ApplicationSer. No. 62/129,932, entitled “VIRTUAL ASSISTANT ACTIVATION,” filed Mar.8, 2015, the content of which are hereby incorporated by reference intheir entirety.

This application is related to U.S. Provisional Patent Application Ser.No. 62/026,532, titled “Raise Gesture Detection in a Device,” filed Jul.18, 2014; and U.S. patent application Ser. No. 12/987,982, titled“Intelligent Automated Assistant,” filed Jan. 10, 2011. The content ofthese applications is hereby incorporated by reference in theirentirety.

BACKGROUND 1. Field

The present disclosure relates generally to intelligent automatedassistants and, more specifically, to techniques for triggeringintelligent automated assistants.

2. Description of Related Art

Intelligent automated assistants (or virtual assistants) providebeneficial interfaces between human users and electronic devices.Exemplary virtual assistants allow users to interact with devices orsystems using natural language in spoken and/or text forms. A user canprovide a spoken input containing a user request to a virtual assistantoperating on an electronic device. The virtual assistant interprets theuser's intent from the spoken input and operationalizes the user'sintent into one or more tasks. The tasks can then be performed byexecuting one or more services of the electronic device, therebyreturning relevant output responsive to the user request.

BRIEF SUMMARY

As virtual assistant become increasingly sophisticated, it can bedesirable to call upon their assistance under increasing numbers ofusage scenarios. Efficient techniques for triggering a virtual assistantare thus helpful. Additionally, in situations where virtual assistantsare executing on battery-powered portable electronic devices, efficienttechniques for triggering virtual assistant while conservingbattery-power are particularly helpful.

In accordance with some embodiments, a method of triggering a virtualassistant on an electronic device comprises: at an electronic devicewith a display, a microphone, and an input device: while the display ison, receiving user input via the input device, the user input meeting apredetermined condition; in accordance with receiving the user inputmeeting the predetermined condition, sampling audio input received viathe microphone; determining whether the audio input comprises a spokentrigger; and in accordance with a determination that audio inputcomprises the spoken trigger, triggering a virtual assistant session.

In accordance with some embodiments, a method of triggering a virtualassistant on an electronic device comprises: at an electronic devicewith a display and a microphone: detecting a software event meeting apredetermined condition; in accordance with a determination that thesoftware event meeting the condition is detected, sampling audio inputreceived via the microphone; determining whether audio input receivedvia the microphone comprises a spoken trigger; and in accordance with adetermination that the audio input comprises the spoken trigger,triggering a virtual assistant session.

In accordance with some embodiments, a method of triggering a virtualassistant on an electronic device comprises: at an electronic devicewith a display, a microphone, and an input device: receiving user inputvia the input device, the user input meeting a predetermined condition;in accordance with receiving the user input meeting the predeterminedcondition, sampling audio input received via the microphone; determiningwhether the audio input comprises a spoken trigger; in accordance with adetermination that audio input comprises the spoken trigger: triggeringa virtual assistant session, and providing a haptic output.

In accordance with some embodiments, a method of triggering a virtualassistant on an electronic device comprises: at an electronic devicewith a display and a microphone: sampling audio input received via themicrophone and determining whether the audio input represents a task;while sampling audio input, receiving instruction to cease sampling ofaudio input; providing output acknowledging the received instruction tocease the sampling of audio input; and after providing the output,continuing the sampling of audio input and determining whether the audioinput comprises a task, for a duration, then ceasing the sampling ofaudio input.

In accordance with some embodiments, an electronic device comprises: adisplay; one or more processors; a memory; and one or more programs,wherein the one or more programs are stored in memory and configured tobe executed by the one or more processors, the one or more programsincluding instructions for: while the display is on, receiving userinput via an input device, the user input meeting a predeterminedcondition; in accordance with receiving the user input meeting thepredetermined condition, sampling audio input received via a microphone;determining whether the audio input comprises a spoken trigger; and inaccordance with a determination that audio input comprises the spokentrigger, triggering a virtual assistant session.

In accordance with some embodiments, an electronic device comprises: adisplay; one or more processors; a memory; and one or more programs,wherein the one or more programs are stored in memory and configured tobe executed by the one or more processors, the one or more programsincluding instructions for: detecting a software event meeting apredetermined condition; in accordance with a determination that thesoftware event meeting the condition is detected, sampling audio inputreceived via a microphone; determining whether audio input received viathe microphone comprises a spoken trigger; and in accordance with adetermination that the audio input comprises the spoken trigger,triggering a virtual assistant session.

In accordance with some embodiments, an electronic device comprises: adisplay; one or more processors; a memory; and one or more programs,wherein the one or more programs are stored in memory and configured tobe executed by the one or more processors, the one or more programsincluding instructions for: receiving user input via the input device,the user input meeting a predetermined condition; in accordance withreceiving the user input meeting the predetermined condition, samplingaudio input received via a microphone; determining whether the audioinput comprises a spoken trigger; in accordance with a determinationthat audio input comprises the spoken trigger: triggering a virtualassistant session, and providing a haptic output.

In accordance with some embodiments, an electronic device comprises: adisplay; one or more processors; a memory; and one or more programs,wherein the one or more programs are stored in memory and configured tobe executed by the one or more processors, the one or more programsincluding instructions for: sampling audio input received via amicrophone and determine whether the audio input represents a task;while sampling audio input, receiving instruction to cease sampling ofaudio input; providing output acknowledging the received instruction tocease the sampling of audio input; and after providing the output,continuing the sampling of audio input and determining whether the audioinput comprises a task, for a duration, then cease the sampling of audioinput.

In accordance with some embodiments, a non-transitory computer readablestorage medium stores one or more programs, the one or more programscomprising instructions, which when executed by an electronic devicewith a display, a microphone, and an input device, cause the electronicdevice to: while the display is on, receive user input via the inputdevice, the user input meeting a predetermined condition; in accordancewith receiving the user input meeting the predetermined condition,sample audio input received via the microphone; determine whether theaudio input comprises a spoken trigger; and in accordance with adetermination that audio input comprises the spoken trigger, trigger avirtual assistant session.

In accordance with some embodiments, a non-transitory computer readablestorage medium stores one or more programs, the one or more programscomprising instructions, which when executed by an electronic devicewith a display, a microphone, and an input device, cause the electronicdevice to: detect a software event meeting a predetermined condition; inaccordance with a determination that the software event meeting thecondition is detected, sample audio input received via the microphone;determine whether audio input received via the microphone comprises aspoken trigger; and in accordance with a determination that the audioinput comprises the spoken trigger, trigger a virtual assistant session.

In accordance with some embodiments, a non-transitory computer readablestorage medium stores one or more programs, the one or more programscomprising instructions, which when executed by an electronic devicewith a display, a microphone, and an input device, cause the electronicdevice to: receive user input via the input device, the user inputmeeting a predetermined condition; in accordance with receiving the userinput meeting the predetermined condition, sample audio input receivedvia the microphone; determine whether the audio input comprises a spokentrigger; in accordance with a determination that audio input comprisesthe spoken trigger: trigger a virtual assistant session, and provide ahaptic output.

In accordance with some embodiments, a non-transitory computer readablestorage medium stores one or more programs, the one or more programscomprising instructions, which when executed by an electronic devicewith a display, a microphone, and an input device, cause the electronicdevice to: sample audio input received via the microphone and determinewhether the audio input represents a task; while sampling audio input,receive instruction to cease sampling of audio input; provide outputacknowledging the received instruction to cease the sampling of audioinput; and after providing the output, continue the sampling of audioinput and determine whether the audio input comprises a task, for aduration, then cease the sampling of audio input.

In accordance with some embodiments, an electronic device comprises:while a displaying means is on, means for receiving user input via theinput device, the user input meeting a predetermined condition; meansfor, in accordance with receiving the user input meeting thepredetermined condition, sampling audio input received via a microphone;means for determining whether the audio input comprises a spokentrigger; and means for, in accordance with a determination that audioinput comprises the spoken trigger, triggering a virtual assistantsession.

In accordance with some embodiments, an electronic device comprises:means for detecting a software event meeting a predetermined condition;means for, in accordance with a determination that the software eventmeeting the condition is detected, sampling audio input received via amicrophone; means for determining whether audio input received via themicrophone comprises a spoken trigger; and means for, in accordance witha determination that the audio input comprises the spoken trigger,triggering a virtual assistant session.

In accordance with some embodiments, an electronic device comprises:means for receiving user input via an input device, the user inputmeeting a predetermined condition; means for, in accordance withreceiving the user input meeting the predetermined condition, samplingaudio input received via a microphone; means for determining whether theaudio input comprises a spoken trigger; means for, in accordance with adetermination that audio input comprises the spoken trigger: triggeringa virtual assistant session, and providing a haptic output.

In accordance with some embodiments, an electronic device comprises:means for sampling audio input received via a microphone and determiningwhether the audio input represents a task; means for, while samplingaudio input, receiving instruction to cease sampling of audio input;means for providing output acknowledging the received instruction tocease the sampling of audio input; and means for, after providing theoutput, continuing the sampling of audio input and determining whetherthe audio input comprises a task, for a duration, then ceasing thesampling of audio input.

In accordance with some embodiments, an electronic device comprises: adisplay; a microphone; an input device; and a processing unit coupled tothe display, the microphone, and the input device, the processing unitconfigured to: while the display is on, receive user input via the inputdevice, the user input meeting a predetermined condition; in accordancewith receiving the user input meeting the predetermined condition,sample audio input received via the microphone; determine whether theaudio input comprises a spoken trigger; and in accordance with adetermination that audio input comprises the spoken trigger, trigger avirtual assistant session.

In accordance with some embodiments, an electronic device comprises: adisplay; a microphone; and a processing unit coupled to the display, themicrophone, and the input device, the processing unit configured to:detect a software event meeting a predetermined condition; in accordancewith a determination that the software event meeting the condition isdetected, sample audio input received via the microphone; determinewhether audio input received via the microphone comprises a spokentrigger; and in accordance with a determination that the audio inputcomprises the spoken trigger, trigger a virtual assistant session.

In accordance with some embodiments, an electronic device comprises: adisplay; a microphone; an input device; and a processing unit coupled tothe display, the microphone, and the input device, the processing unitconfigured to: receive user input via the input device, the user inputmeeting a predetermined condition; in accordance with receiving the userinput meeting the predetermined condition, sample audio input receivedvia the microphone; determine whether the audio input comprises a spokentrigger; in accordance with a determination that audio input comprisesthe spoken trigger: trigger a virtual assistant session, and provide ahaptic output.

In accordance with some embodiments, an electronic device comprises: adisplay; a microphone; a input device and a processing unit coupled tothe display, the microphone, and the input device, the processing unitconfigured to: sample audio input received via the microphone anddetermine whether the audio input represents a task; while samplingaudio input, receive instruction to cease sampling of audio input;provide output acknowledging the received instruction to cease thesampling of audio input; and after providing the output, continue thesampling of audio input and determine whether the audio input comprisesa task, for a duration, then cease the sampling of audio input.

In accordance with some embodiments, a transitory computer readablestorage medium stores one or more programs, the one or more programscomprising instructions, which when executed by an electronic devicewith a display, a microphone, and an input device, cause the electronicdevice to: while the display is on, receive user input via the inputdevice, the user input meeting a predetermined condition; in accordancewith receiving the user input meeting the predetermined condition,sample audio input received via the microphone; determine whether theaudio input comprises a spoken trigger; and in accordance with adetermination that audio input comprises the spoken trigger, trigger avirtual assistant session.

In accordance with some embodiments, a transitory computer readablestorage medium stores one or more programs, the one or more programscomprising instructions, which when executed by an electronic devicewith a display, a microphone, and an input device, cause the electronicdevice to: detect a software event meeting a predetermined condition; inaccordance with a determination that the software event meeting thecondition is detected, sample audio input received via the microphone;determine whether audio input received via the microphone comprises aspoken trigger; and in accordance with a determination that the audioinput comprises the spoken trigger, trigger a virtual assistant session.

In accordance with some embodiments, a transitory computer readablestorage medium stores one or more programs, the one or more programscomprising instructions, which when executed by an electronic devicewith a display, a microphone, and an input device, cause the electronicdevice to: receive user input via the input device, the user inputmeeting a predetermined condition; in accordance with receiving the userinput meeting the predetermined condition, sample audio input receivedvia the microphone; determine whether the audio input comprises a spokentrigger; in accordance with a determination that audio input comprisesthe spoken trigger: trigger a virtual assistant session, and provide ahaptic output.

In accordance with some embodiments, a transitory computer readablestorage medium stores one or more programs, the one or more programscomprising instructions, which when executed by an electronic devicewith a display, a microphone, and an input device, cause the electronicdevice to: sample audio input received via the microphone and determinewhether the audio input represents a task; while sampling audio input,receive instruction to cease sampling of audio input; provide outputacknowledging the received instruction to cease the sampling of audioinput; and after providing the output, continue the sampling of audioinput and determine whether the audio input comprises a task, for aduration, then cease the sampling of audio input.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

BRIEF DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1 illustrates a system and environment for implementing a digitalassistant in accordance with some embodiments.

FIG. 2A is a block diagram illustrating a portable multifunction deviceimplementing the client-side portion of a digital assistant inaccordance with some embodiments.

FIG. 2B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 3 illustrates a portable multifunction device implementing theclient-side portion of a digital assistant in accordance with someembodiments.

FIG. 4 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 5A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 5B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 6A illustrates a personal electronic device in accordance with someembodiments.

FIG. 6B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIG. 7A illustrates a digital assistant system or a server portionthereof in accordance with some embodiments.

FIG. 7B illustrates the functions of the digital assistant shown in FIG.8A in accordance with some embodiments.

FIG. 7C illustrates a portion of an ontology in accordance with someembodiments.

FIG. 8A-8C illustrate exemplary techniques for triggering a virtualassistant in accordance with some embodiments.

FIG. 9A-9C illustrate exemplary techniques for triggering a virtualassistant in accordance with some embodiments.

FIG. 10A-10D illustrate exemplary techniques for triggering a virtualassistant in accordance with some embodiments.

FIG. 11A-11C illustrate exemplary techniques for triggering a virtualassistant in accordance with some embodiments.

FIG. 12 is a flow diagram illustrating a method of triggering a virtualassistant in accordance with some embodiments.

FIG. 13 is a flow diagram illustrating a method of triggering a virtualassistant in accordance with some embodiments.

FIG. 14 is a flow diagram illustrating a method of triggering a virtualassistant in accordance with some embodiments.

FIG. 15 is a flow diagram illustrating a method of triggering a virtualassistant in accordance with some embodiments.

FIG. 16 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 17 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 18 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 19 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 20A-20E illustrate exemplary techniques for interacting with avirtual assistant in accordance with some embodiments.

FIG. 21 is a flow diagram illustrating a method of interacting with avirtual assistant in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

In the following description of the disclosure and embodiments,reference is made to the accompanying drawings in which it is shown byway of illustration specific embodiments that can be practiced. It is tobe understood that other embodiments and examples can be practiced andchanges can be made without departing from the scope of the disclosure.

Virtual assistant services can be computationally intensive. Forexample, a virtual assistant optionally samples audio input from a userby activating a microphone, its associated circuitry, and correspondingsoftware processes, thereby drawing computing resources. There is a needfor electronic devices that provide virtual assistant services to employtechniques that reduce processor and associated battery power draw, suchthat computing resources otherwise wasted on processing unnecessary userinputs are conserved while providing an effective virtual assistantinterface.

Below, FIGS. 1, 2A, 7A-7B, and 16-19 provide a description of exemplarydevices for performing the techniques for transitioning betweencomputing devices. FIGS. 8A-8C, 9A-9C, 10A-10D, and 11A-11C illustrateexemplary user interfaces for transitioning between computing devices.The user interfaces in the figures are also used to illustrate theprocesses described below, including the processes in FIGS. 12-15 .

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first input could be termed a second input, and,similarly, a second input could be termed a first input, withoutdeparting from the scope of the various described examples. The firstinput and the second input can both be outputs and, in some cases, canbe separate and different inputs.

The terminology used in the description of the various describedexamples herein is for the purpose of describing particular examplesonly and is not intended to be limiting. As used in the description ofthe various described examples and the appended claims, the singularforms “a”, “an,” and “the” are intended to include the plural forms aswell, unless the context clearly indicates otherwise. It will also beunderstood that the term “and/or” as used herein refers to andencompasses any and all possible combinations of one or more of theassociated listed items. It will be further understood that the terms“includes,” “including,” “comprises,” and/or “comprising,” when used inthis specification, specify the presence of stated features, integers,steps, operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

1 System and Environment

FIG. 1 illustrates a block diagram of system 100 according to variousexamples. In some examples, system 100 can implement a digitalassistant. The terms “digital assistant,” “virtual assistant,”“intelligent automated assistant,” or “automatic digital assistant” canrefer to any information processing system that interprets naturallanguage input in spoken and/or textual form to infer user intent, andperforms actions based on the inferred user intent. For example, to acton an inferred user intent, the system can perform one or more of thefollowing: identifying a task flow with steps and parameters designed toaccomplish the inferred user intent, inputting specific requirementsfrom the inferred user intent into the task flow; executing the taskflow by invoking programs, methods, services, APIs, or the like; andgenerating output responses to the user in an audible (e.g., speech)and/or visual form.

Specifically, a digital assistant can be capable of accepting a userrequest at least partially in the form of a natural language command,request, statement, narrative, and/or inquiry. Typically, the userrequest can seek either an informational answer or performance of a taskby the digital assistant. A satisfactory response to the user requestcan be a provision of the requested informational answer, a performanceof the requested task, or a combination of the two. For example, a usercan ask the digital assistant a question, such as “Where am I rightnow?” Based on the user's current location, the digital assistant cananswer, “You are in Central Park near the west gate.” The user can alsorequest the performance of a task, for example, “Please invite myfriends to my girlfriend's birthday party next week.” In response, thedigital assistant can acknowledge the request by saying “Yes, rightaway,” and then send a suitable calendar invite on behalf of the user toeach of the user's friends listed in the user's electronic address book.During performance of a requested task, the digital assistant cansometimes interact with the user in a continuous dialogue involvingmultiple exchanges of information over an extended period of time. Thereare numerous other ways of interacting with a digital assistant torequest information or performance of various tasks. In addition toproviding verbal responses and taking programmed actions, the digitalassistant can also provide responses in other visual or audio forms,e.g., as text, alerts, music, videos, animations, etc.

As shown in FIG. 1 , in some examples, a digital assistant can beimplemented according to a client-server model. The digital assistantcan include client-side portion 102 (hereafter “DA client 102”) executedon user device 104 and server-side portion 106 (hereafter “DA server106”) executed on server system 108. DA client 102 can communicate withDA server 106 through one or more networks 110. DA client 102 canprovide client-side functionalities such as user-facing input and outputprocessing and communication with DA server 106. DA server 106 canprovide server-side functionalities for any number of DA clients 102each residing on a respective user device 104.

In some examples, DA server 106 can include client-facing I/O interface112, one or more processing modules 114, data and models 116, and I/Ointerface to external services 118. The client-facing I/O interface 112can facilitate the client-facing input and output processing for DAserver 106. One or more processing modules 114 can utilize data andmodels 116 to process speech input and determine the user's intent basedon natural language input. Further, one or more processing modules 114perform task execution based on inferred user intent. In some examples,DA server 106 can communicate with external services 120 throughnetwork(s) 110 for task completion or information acquisition. I/Ointerface to external services 118 can facilitate such communications.

User device 104 can be any suitable electronic device. For example, userdevices can be a portable multifunctional device (e.g., device 200,described below with reference to FIG. 2A), a multifunctional device(e.g., device 400, described below with reference to FIG. 4 ), or apersonal electronic device (e.g., device 600, described below withreference to FIG. 6A-B.) A portable multifunctional device can be, forexample, a mobile telephone that also contains other functions, such asPDA and/or music player functions. Specific examples of portablemultifunction devices can include the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other examples of portablemultifunction devices can include, without limitation, laptop or tabletcomputers. Further, in some examples, user device 104 can be anon-portable multifunctional device. In particular, user device 104 canbe a desktop computer, a game console, a television, or a televisionset-top box. In some examples, user device 104 can include atouch-sensitive surface (e.g., touch screen displays and/or touchpads).Further, user device 104 can optionally include one or more otherphysical user-interface devices, such as a physical keyboard, a mouse,and/or a joystick. Various examples of electronic devices, such asmultifunctional devices, are described below in greater detail.

Examples of communication network(s) 110 can include local area networks(LAN) and wide area networks (WAN), e.g., the Internet. Communicationnetwork(s) 110 can be implemented using any known network protocol,including various wired or wireless protocols, such as, for example,Ethernet, Universal Serial Bus (USB), FIREWIRE, Global System for MobileCommunications (GSM), Enhanced Data GSM Environment (EDGE), codedivision multiple access (CDMA), time division multiple access (TDMA),Bluetooth, Wi-Fi, voice over Internet Protocol (VoIP), Wi-MAX, or anyother suitable communication protocol.

Server system 108 can be implemented on one or more standalone dataprocessing apparatus or a distributed network of computers. In someexamples, server system 108 can also employ various virtual devicesand/or services of third-party service providers (e.g., third-partycloud service providers) to provide the underlying computing resourcesand/or infrastructure resources of server system 108.

In some examples, user device 104 can communicate with DA server 106 viasecond user device 122. Second user device 122 can be similar oridentical to user device 104. For example, second user device 122 can besimilar to any one of devices 200, 400, or 600, described below withreference to FIGS. 2A, 4, and 6A-B, respectively. User device 104 can beconfigured to communicatively couple to second user device 122 via adirect communication connection, such as Bluetooth, NFC, BTLE, or thelike, or via a wired or wireless network, such as a local Wi-Fi network.In some examples, second user device 122 can be configured to act as aproxy between user device 104 and DA server 106. For example, DA client102 of user device 104 can be configured to transmit information (e.g.,a user request received at user device 104) to DA server 106 via seconduser device 122. DA server 106 can process the information and returnrelevant data (e.g., data content responsive to the user request) touser device 104 via second user device 122.

In some examples, user device 104 can be configured to communicateabbreviated requests for data to second user device 122 to reduce theamount of information transmitted from user device 104. Second userdevice 122 can be configured to determine supplemental information toadd to the abbreviated request to generate a complete request totransmit to DA server 106. This system architecture can advantageouslyallow user device 104 having limited communication capabilities and/orlimited battery power (e.g., a watch or a similar compact electronicdevice) to access services provided by DA server 106 by using seconduser device 122, having greater communication capabilities and/orbattery power (e.g., a mobile phone, laptop computer, tablet computer,or the like), as a proxy to DA server 106. While only two user devices104 and 122 are shown in FIG. 1 , it should be appreciated that system100 can include any number and type of user devices configured in thisproxy configuration to communicate with DA server system 106.

Although the digital assistant shown in FIG. 1 can include both aclient-side portion (e.g., DA client 102) and a server-side portion(e.g., DA server 106), in some examples, the functions of a digitalassistant can be implemented as a standalone application installed on auser device. In addition, the divisions of functionalities between theclient and server portions of the digital assistant can vary indifferent implementations. For instance, in some examples, the DA clientcan be a thin-client that provides only user-facing input and outputprocessing functions, and delegates all other functionalities of thedigital assistant to a backend server.

2. Electronic Devices

Attention is now directed toward embodiments of electronic devices forimplementing the client-side portion of a digital assistant. FIG. 2A isa block diagram illustrating portable multifunction device 200 withtouch-sensitive display system 212 in accordance with some embodiments.Touch-sensitive display 212 is sometimes called a “touch screen” forconvenience and is sometimes known as or called a “touch-sensitivedisplay system.” Device 200 includes memory 202 (which optionallyincludes one or more computer-readable storage mediums), memorycontroller 222, one or more processing units (CPUs) 220, peripheralsinterface 218, RF circuitry 208, audio circuitry 210, speaker 211,microphone 213, input/output (I/O) subsystem 206, other input controldevices 216, and external port 224. Device 200 optionally includes oneor more optical sensors 264. Device 200 optionally includes one or morecontact intensity sensors 265 for detecting intensity of contacts ondevice 200 (e.g., a touch-sensitive surface such as touch-sensitivedisplay system 212 of device 200). Device 200 optionally includes one ormore tactile output generators 267 for generating tactile outputs ondevice 200 (e.g., generating tactile outputs on a touch-sensitivesurface such as touch-sensitive display system 212 of device 200 ortouchpad 455 of device 400). These components optionally communicateover one or more communication buses or signal lines 203.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 200 is only one example of aportable multifunction device, and that device 200 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 2A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 202 optionally includes one or more computer-readable storagemediums. The computer-readable storage mediums is, optionally, tangibleand non-transitory. Memory 202 optionally includes high-speed randomaccess memory and optionally includes non-volatile memory, such as oneor more magnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 222optionally controls access to memory 202 by other components of device200.

In some examples, a non-transitory computer-readable storage medium ofmemory 202 can be used to store instructions (e.g., for performingaspects of methods 1200, 1300, 1400, or 1500, described below) for useby or in connection with an instruction execution system, apparatus, ordevice, such as a computer-based system, processor-containing system, orother system that can fetch the instructions from the instructionexecution system, apparatus, or device and execute the instructions. Inother examples, the instructions (e.g., for performing aspects ofmethods 1200, 1300, 1400, or 1500, described below) can be stored on anon-transitory computer-readable storage medium (not shown) of theserver system 108 or can be divided between the non-transitorycomputer-readable storage medium of memory 202 and the non-transitorycomputer-readable storage medium of server system 108. In the context ofthis document, a “non-transitory computer-readable storage medium” canbe any medium that can contain or store the program for use by or inconnection with the instruction execution system, apparatus, or device.

Peripherals interface 218 can be used to couple input and outputperipherals of the device to CPU 220 and memory 202. The one or moreprocessors 220 run or execute various software programs and/or sets ofinstructions stored in memory 202 to perform various functions fordevice 200 and to process data. In some embodiments, peripheralsinterface 218, CPU 220, and memory controller 222 is, optionally,implemented on a single chip, such as chip 204. In some otherembodiments, they are, optionally, be implemented on separate chips.

RF (radio frequency) circuitry 208 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 208 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 208 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 208 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 208optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 210, speaker 211, and microphone 213 provide an audiointerface between a user and device 200. Audio circuitry 210 receivesaudio data from peripherals interface 218, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 211.Speaker 211 converts the electrical signal to human-audible sound waves.Audio circuitry 210 also receives electrical signals converted bymicrophone 213 from sound waves. Audio circuitry 210 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 218 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 202 and/or RF circuitry 208by peripherals interface 218. In some embodiments, audio circuitry 210also includes a headset jack (e.g., 312, FIG. 3 ). The headset jackprovides an interface between audio circuitry 210 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 206 couples input/output peripherals on device 200, suchas touch screen 212 and other input control devices 216, to peripheralsinterface 218. I/O subsystem 206 optionally includes display controller256, optical sensor controller 258, intensity sensor controller 259,haptic feedback controller 261, and one or more input controllers 260for other input or control devices. The one or more input controllers260 receive/send electrical signals from/to other input control devices216. The other input control devices 216 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 260 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 308, FIG.3 ) optionally include an up/down button for volume control of speaker211 and/or microphone 213. The one or more buttons optionally include apush button (e.g., 306, FIG. 3 ).

A quick press of the push button optionally disengages a lock of touchscreen 212 or begin a process that uses gestures on the touch screen tounlock the device, as described in U.S. patent application Ser. No.11/322,549, “Unlocking a Device by Performing Gestures on an UnlockImage,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is herebyincorporated by reference in its entirety. A longer press of the pushbutton (e.g., 306) optionally turns power to device 200 on or off. Thefunctionality of one or more of the buttons are, optionally, usercustomizable. Touch screen 212 is used to implement virtual or softbuttons and one or more soft keyboards.

Touch-sensitive display 212 provides an input interface and an outputinterface between the device and a user. Display controller 256 receivesand/or sends electrical signals from/to touch screen 212. Touch screen212 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally correspond to user-interface objects.

Touch screen 212 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 212 and display controller 256 (along with anyassociated modules and/or sets of instructions in memory 202) detectcontact (and any movement or breaking of the contact) on touch screen212 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 212. In an exemplaryembodiment, a point of contact between touch screen 212 and the usercorresponds to a finger of the user.

Touch screen 212 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 212 and display controller256 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 212. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 212 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 212 displays visual output from device 200, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 212 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 212 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 212 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 200optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch screen 212 or anextension of the touch-sensitive surface formed by the touch screen.

Device 200 also includes power system 262 for powering the variouscomponents. Power system 262 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 200 optionally also include one or more optical sensors 264. FIG.2A shows an optical sensor coupled to optical sensor controller 258 inI/O subsystem 206. Optical sensor 264 optionally includes charge-coupleddevice (CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 264 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module243 (also called a camera module), optical sensor 264 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 200, opposite touch screen display 212on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 264 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 264 is, optionally, used along with the touch screendisplay for both video conferencing and still and/or video imageacquisition.

Device 200 optionally also includes one or more contact intensitysensors 265. FIG. 2A shows a contact intensity sensor coupled tointensity sensor controller 259 in I/O subsystem 206. Contact intensitysensor 265 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 265 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 212). In some embodiments, at least one contact intensitysensor is located on the back of device 200, opposite touch screendisplay 212, which is located on the front of device 200.

Device 200 optionally also includes one or more proximity sensors 266.FIG. 2A shows proximity sensor 266 coupled to peripherals interface 218.Alternately, proximity sensor 266 is, optionally, coupled to inputcontroller 260 in I/O subsystem 206. Proximity sensor 266 optionallyperforms as described in U.S. patent application Ser. Nos. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 212 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 200 optionally also includes one or more tactile outputgenerators 267. FIG. 2A shows a tactile output generator coupled tohaptic feedback controller 261 in I/O subsystem 206. Tactile outputgenerator 267 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 265 receives tactile feedbackgeneration instructions from haptic feedback module 233 and generatestactile outputs on device 200 that are capable of being sensed by a userof device 200. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 212) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 200) or laterally (e.g., back and forth inthe same plane as a surface of device 200). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 200, opposite touch screen display 212, which is located on thefront of device 200.

Device 200 optionally also includes one or more accelerometers 268. FIG.2A shows accelerometer 268 coupled to peripherals interface 218.Alternately, accelerometer 268 is, optionally, coupled to an inputcontroller 260 in I/O subsystem 206. Accelerometer 268 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 200 optionallyincludes, in addition to accelerometer(s) 268, a magnetometer (notshown) and a GPS (or GLONASS or other global navigation system) receiver(not shown) for obtaining information concerning the location andorientation (e.g., portrait or landscape) of device 200.

In some embodiments, the software components stored in memory 202include operating system 226, communication module (or set ofinstructions) 228, contact/motion module (or set of instructions) 230,graphics module (or set of instructions) 232, text input module (or setof instructions) 234, Global Positioning System (GPS) module (or set ofinstructions) 235, Digital Assistant Client Module 229, and applications(or sets of instructions) 236. Further, memory 202 can store data andmodels, such as user data and models 231. Furthermore, in someembodiments, memory 202 (FIG. 2A) or 470 (FIG. 4 ) stores device/globalinternal state 257, as shown in FIGS. 2A and 4 . Device/global internalstate 257 includes one or more of: active application state, indicatingwhich applications, if any, are currently active; display state,indicating what applications, views or other information occupy variousregions of touch screen display 212; sensor state, including informationobtained from the device's various sensors and input control devices216; and location information concerning the device's location and/orattitude.

Operating system 226 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 228 facilitates communication with other devicesover one or more external ports 224 and also includes various softwarecomponents for handling data received by RF circuitry 208 and/orexternal port 224. External port 224 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 230 optionally detects contact with touch screen212 (in conjunction with display controller 256) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 230 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 230 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 230 and display controller 256 detect contact on atouchpad.

In some embodiments, contact/motion module 230 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 200). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 230 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 232 includes various known software components forrendering and displaying graphics on touch screen 212 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 232 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 232 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 256.

Haptic feedback module 233 includes various software components forgenerating instructions used by tactile output generator(s) 267 toproduce tactile outputs at one or more locations on device 200 inresponse to user interactions with device 200. In some embodiments,event monitor 271 sends requests to the peripherals interface 218 atpredetermined intervals. In response, peripherals interface 218transmits event information. In other embodiments, peripherals interface218 transmits event information only when there is a significant event(e.g., receiving an input above a predetermined noise threshold and/orfor more than a predetermined duration).

Text input module 234, which is, optionally, a component of graphicsmodule 232, provides soft keyboards for entering text in variousapplications (e.g., contacts 237, e mail 240, IM 241, browser 247, andany other application that needs text input).

GPS module 235 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 238 foruse in location-based dialing; to camera 243 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Digital assistant client module 229 can include various client-sidedigital assistant instructions to provide the client-sidefunctionalities of the digital assistant. For example, digital assistantclient module 229 can be capable of accepting voice input (e.g., speechinput), text input, touch input, and/or gestural input through varioususer interfaces (e.g., microphone 213, accelerometer(s) 268,touch-sensitive display system 212, optical sensor(s) 264, other inputcontrol devices 216, etc.) of portable multifunction device 200. Digitalassistant client module 229 can also be capable of providing output inaudio (e.g., speech output), visual, and/or tactile forms throughvarious output interfaces (e.g., speaker 211, touch-sensitive displaysystem 212, tactile output generator(s) 267, etc.) of portablemultifunction device 200. For example, output can be provided as voice,sound, alerts, text messages, menus, graphics, videos, animations,vibrations, and/or combinations of two or more of the above. Duringoperation, digital assistant client module 229 can communicate with DAserver 106 using RF circuitry 208.

User data and models 231 can include various data associated with theuser (e.g., user-specific vocabulary data, user preference data,user-specified name pronunciations, data from the user's electronicaddress book, to-do lists, shopping lists, etc.) to provide theclient-side functionalities of the digital assistant. Further, user dataand models 231 can includes various models (e.g., speech recognitionmodels, statistical language models, natural language processing models,ontology, task flow models, service models, etc.) for processing userinput and determining user intent.

In some examples, digital assistant client module 229 can utilize thevarious sensors, subsystems, and peripheral devices of portablemultifunction device 200 to gather additional information from thesurrounding environment of the portable multifunction device 200 toestablish a context associated with a user, the current userinteraction, and/or the current user input. In some examples, digitalassistant client module 229 can provide the contextual information or asubset thereof with the user input to DA server 106 to help infer theuser's intent. In some examples, the digital assistant can also use thecontextual information to determine how to prepare and deliver outputsto the user. Contextual information can be referred to as context data.

In some examples, the contextual information that accompanies the userinput can include sensor information, e.g., lighting, ambient noise,ambient temperature, images or videos of the surrounding environment,etc. In some examples, the contextual information can also include thephysical state of the device, e.g., device orientation, device location,device temperature, power level, speed, acceleration, motion patterns,cellular signals strength, etc. In some examples, information related tothe software state of DA server 106, e.g., running processes, installedprograms, past and present network activities, background services,error logs, resources usage, etc., and of portable multifunction device200 can be provided to DA server 106 as contextual informationassociated with a user input.

In some examples, the digital assistant client module 229 canselectively provide information (e.g., user data 231) stored on theportable multifunction device 200 in response to requests from DA server106. In some examples, digital assistant client module 229 can alsoelicit additional input from the user via a natural language dialogue orother user interfaces upon request by DA server 106. Digital assistantclient module 229 can pass the additional input to DA server 106 to helpDA server 106 in intent deduction and/or fulfillment of the user'sintent expressed in the user request.

A more detailed description of a digital assistant is described belowwith reference to FIGS. 7A-C. It should be recognized that digitalassistant client module 229 can include any number of the sub-modules ofdigital assistant module 726 described below.

Applications 236 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 237 (sometimes called an address book or contact        list);    -   Telephone module 238;    -   Video conference module 239;    -   E-mail client module 240;    -   Instant messaging (IM) module 241;    -   Workout support module 242;    -   Camera module 243 for still and/or video images;    -   Image management module 244;    -   Video player module;    -   Music player module;    -   Browser module 247;    -   Calendar module 248;    -   Widget modules 249, which optionally include one or more of:        weather widget 249-1, stocks widget 249-2, calculator widget        249-3, alarm clock widget 249-4, dictionary widget 249-5, and        other widgets obtained by the user, as well as user-created        widgets 249-6;    -   Widget creator module 250 for making user-created widgets 249-6;    -   Search module 251;    -   Video and music player module 252, which merges video player        module and music player module;    -   Notes module 253;    -   Map module 254; and/or    -   Online video module 255.

Examples of other applications 236 that are, optionally, stored inmemory 202 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, and text input module234, contacts module 237 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 292 ofcontacts module 237 in memory 202 or memory 470), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 238, video conference module 239, e-mail 240, or IM 241; andso forth.

In conjunction with RF circuitry 208, audio circuitry 210, speaker 211,microphone 213, touch screen 212, display controller 256, contact/motionmodule 230, graphics module 232, and text input module 234, telephonemodule 238 are, optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 237, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 208, audio circuitry 210, speaker 211,microphone 213, touch screen 212, display controller 256, optical sensor264, optical sensor controller 258, contact/motion module 230, graphicsmodule 232, text input module 234, contacts module 237, and telephonemodule 238, video conference module 239 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, and textinput module 234, e-mail client module 240 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 244,e-mail client module 240 makes it very easy to create and send e-mailswith still or video images taken with camera module 243.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, and textinput module 234, the instant messaging module 241 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, textinput module 234, GPS module 235, map module 254, and music playermodule, workout support module 242 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 212, display controller 256, opticalsensor(s) 264, optical sensor controller 258, contact/motion module 230,graphics module 232, and image management module 244, camera module 243includes executable instructions to capture still images or video(including a video stream) and store them into memory 202, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 202.

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, text input module 234,and camera module 243, image management module 244 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, and textinput module 234, browser module 247 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, textinput module 234, e-mail client module 240, and browser module 247,calendar module 248 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, textinput module 234, and browser module 247, widget modules 249 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 249-1, stocks widget 249-2, calculator widget249-3, alarm clock widget 249-4, and dictionary widget 249-5) or createdby the user (e.g., user-created widget 249-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, textinput module 234, and browser module 247, the widget creator module 250are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, and text input module234, search module 251 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 202 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, audio circuitry 210,speaker 211, RF circuitry 208, and browser module 247, video and musicplayer module 252 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 212 or on an external, connected display via externalport 224). In some embodiments, device 200 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, and text input module234, notes module 253 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, textinput module 234, GPS module 235, and browser module 247, map module 254are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, audio circuitry 210,speaker 211, RF circuitry 208, text input module 234, e-mail clientmodule 240, and browser module 247, online video module 255 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 224), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 241, rather than e-mail client module 240, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule are, optionally, combined with music player module into a singlemodule (e.g., video and music player module 252, FIG. 2A). In someembodiments, memory 202 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 202 optionallystores additional modules and data structures not described above.

In some embodiments, device 200 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device200, the number of physical input control devices (such as push buttons,dials, and the like) on device 200 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 200 to a main, home, or root menu from any userinterface that is displayed on device 200. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 2B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 202 (FIG. 2A) or 470 (FIG. 4 ) includes event sorter 270 (e.g.,in operating system 226) and a respective application 236-1 (e.g., anyof the aforementioned applications 237-251, 255, 480-490).

Event sorter 270 receives event information and determines theapplication 236-1 and application view 291 of application 236-1 to whichto deliver the event information. Event sorter 270 includes eventmonitor 271 and event dispatcher module 274. In some embodiments,application 236-1 includes application internal state 292, whichindicates the current application view(s) displayed on touch-sensitivedisplay 212 when the application is active or executing. In someembodiments, device/global internal state 257 is used by event sorter270 to determine which application(s) is (are) currently active, andapplication internal state 292 is used by event sorter 270 to determineapplication views 291 to which to deliver event information.

In some embodiments, application internal state 292 includes additionalinformation, such as one or more of: resume information to be used whenapplication 236-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 236-1, a state queue for enabling the user to go back toa prior state or view of application 236-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 271 receives event information from peripherals interface218. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 212, as part of a multi-touchgesture). Peripherals interface 218 transmits information it receivesfrom I/O subsystem 206 or a sensor, such as proximity sensor 266,accelerometer(s) 268, and/or microphone 213 (through audio circuitry210). Information that peripherals interface 218 receives from I/Osubsystem 206 includes information from touch-sensitive display 212 or atouch-sensitive surface.

In some embodiments, event sorter 270 also includes a hit viewdetermination module 272 and/or an active event recognizer determinationmodule 273.

Hit view determination module 272 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 212 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 272 receives information related to subevents of a touch-based gesture. When an application has multiple viewsorganized in a hierarchy, hit view determination module 272 identifies ahit view as the lowest view in the hierarchy which should handle thesub-event. In most circumstances, the hit view is the lowest level viewin which an initiating sub-event occurs (e.g., the first sub-event inthe sequence of sub-events that form an event or potential event). Oncethe hit view is identified by the hit view determination module 272, thehit view typically receives all sub-events related to the same touch orinput source for which it was identified as the hit view.

Active event recognizer determination module 273 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 273 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 273 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 274 dispatches the event information to an eventrecognizer (e.g., event recognizer 280). In embodiments including activeevent recognizer determination module 273, event dispatcher module 274delivers the event information to an event recognizer determined byactive event recognizer determination module 273. In some embodiments,event dispatcher module 274 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 282.

In some embodiments, operating system 226 includes event sorter 270.Alternatively, application 236-1 includes event sorter 270. In yet otherembodiments, event sorter 270 is a stand-alone module, or a part ofanother module stored in memory 202, such as contact/motion module 230.

In some embodiments, application 236-1 includes a plurality of eventhandlers 290 and one or more application views 291, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 291 of the application 236-1 includes one or more event recognizers280. Typically, a respective application view 291 includes a pluralityof event recognizers 280. In other embodiments, one or more of eventrecognizers 280 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 236-1inherits methods and other properties. In some embodiments, a respectiveevent handler 290 includes one or more of: data updater 276, objectupdater 277, GUI updater 278, and/or event data 279 received from eventsorter 270. Event handler 290 optionally utilizes or calls data updater276, object updater 277, or GUI updater 278 to update the applicationinternal state 292. Alternatively, one or more of the application views291 include one or more respective event handlers 290. Also, in someembodiments, one or more of data updater 276, object updater 277, andGUI updater 278 are included in a respective application view 291.

A respective event recognizer 280 receives event information (e.g.,event data 279) from event sorter 270 and identifies an event from theevent information. Event recognizer 280 includes event receiver 282 andevent comparator 284. In some embodiments, event recognizer 280 alsoincludes at least a subset of: metadata 283, and event deliveryinstructions 288 (which optionally include sub-event deliveryinstructions).

Event receiver 282 receives event information from event sorter 270. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 284 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 284 includes eventdefinitions 286. Event definitions 286 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(287-1), event 2 (287-2), and others. In some embodiments, sub-events inan event (287) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (287-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (287-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 212, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 290.

In some embodiments, event definition 287 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 284 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 212, when a touch is detected on touch-sensitivedisplay 212, event comparator 284 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 290, the event comparator uses the result of the hit testto determine which event handler 290 should be activated. For example,event comparator 284 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (287) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 280 determines that the series ofsub-events do not match any of the events in event definitions 286, therespective event recognizer 280 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 280 includes metadata283 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 283 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers optionally interact, or are optionally enabled to interact,with one another. In some embodiments, metadata 283 includesconfigurable properties, flags, and/or lists that indicate whethersub-events are delivered to varying levels in the view or programmatichierarchy.

In some embodiments, a respective event recognizer 280 activates eventhandler 290 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 280 delivers event information associated with theevent to event handler 290. Activating an event handler 290 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 280 throws a flag associated withthe recognized event, and event handler 290 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 288 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 276 creates and updates data used inapplication 236-1. For example, data updater 276 updates the telephonenumber used in contacts module 237, or stores a video file used in videoplayer module. In some embodiments, object updater 277 creates andupdates objects used in application 236-1. For example, object updater277 creates a new user-interface object or updates the position of auser-interface object. GUI updater 278 updates the GUI. For example, GUIupdater 278 prepares display information and sends it to graphics module232 for display on a touch-sensitive display.

In some embodiments, event handler(s) 290 includes or has access to dataupdater 276, object updater 277, and GUI updater 278. In someembodiments, data updater 276, object updater 277, and GUI updater 278are included in a single module of a respective application 236-1 orapplication view 291. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 200 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 3 illustrates a portable multifunction device 200 having a touchscreen 212 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 300.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 302 (not drawn to scalein the figure) or one or more styluses 303 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 200. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 200 also optionally includes one or more physical buttons, suchas “home” or menu button 304. As described previously, menu button 304is, optionally, used to navigate to any application 236 in a set ofapplications that are, optionally, executed on device 200.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 212.

In some embodiments, device 200 includes touch screen 212, menu button304, push button 306 for powering the device on/off and locking thedevice, volume adjustment button(s) 308, subscriber identity module(SIM) card slot 310, headset jack 312, and docking/charging externalport 224. Push button 306 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 200 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 213. Device 200 also, optionally, includes one or morecontact intensity sensors 265 for detecting intensity of contacts ontouch screen 212 and/or one or more tactile output generators 267 forgenerating tactile outputs for a user of device 200.

FIG. 4 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 400 need not be portable. In some embodiments,device 400 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 400 typically includesone or more processing units (CPUs) 410, one or more network or othercommunications interfaces 460, memory 470, and one or more communicationbuses 420 for interconnecting these components. Communication buses 420optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 400 includes input/output (I/O) interface 430 comprising display440, which is typically a touch screen display. I/O interface 430 alsooptionally includes a keyboard and/or mouse (or other pointing device)450 and touchpad 455, tactile output generator 457 for generatingtactile outputs on device 400 (e.g., similar to tactile outputgenerator(s) 267 described above with reference to FIG. 2A), sensors 459(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 265 describedabove with reference to FIG. 2A). Memory 470 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 470 optionally includes one or more storage devicesremotely located from CPU(s) 410. In some embodiments, memory 470 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 202 of portablemultifunction device 200 (FIG. 2A), or a subset thereof. Furthermore,memory 470 optionally stores additional programs, modules, and datastructures not present in memory 202 of portable multifunction device200. For example, memory 470 of device 400 optionally stores drawingmodule 480, presentation module 482, word processing module 484, websitecreation module 486, disk authoring module 488, and/or spreadsheetmodule 490, while memory 202 of portable multifunction device 200 (FIG.2A) optionally does not store these modules.

Each of the above-identified elements in FIG. 4 are, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 470optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 470 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatis, optionally, implemented on, for example, portable multifunctiondevice 200.

FIG. 5A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 200 in accordance withsome embodiments. Similar user interfaces is, optionally, implemented ondevice 400. In some embodiments, user interface 500 includes thefollowing elements, or a subset or superset thereof:

Signal strength indicator(s) 502 for wireless communication(s), such ascellular and Wi-Fi signals;

-   -   Time 504;    -   Bluetooth indicator 505;    -   Battery status indicator 506;    -   Tray 508 with icons for frequently used applications, such as:        -   Icon 516 for telephone module 238, labeled “Phone,” which            optionally includes an indicator 514 of the number of missed            calls or voicemail messages;        -   Icon 518 for e-mail client module 240, labeled “Mail,” which            optionally includes an indicator 510 of the number of unread            e-mails;        -   Icon 520 for browser module 247, labeled “Browser;” and        -   Icon 522 for video and music player module 252, also            referred to as iPod (trademark of Apple Inc.) module 252,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 524 for IM module 241, labeled “Messages;”        -   Icon 526 for calendar module 248, labeled “Calendar;”        -   Icon 528 for image management module 244, labeled “Photos;”        -   Icon 530 for camera module 243, labeled “Camera;”        -   Icon 532 for online video module 255, labeled “Online            Video;”        -   Icon 534 for stocks widget 249-2, labeled “Stocks;”        -   Icon 536 for map module 254, labeled “Maps;”        -   Icon 538 for weather widget 249-1, labeled “Weather;”        -   Icon 540 for alarm clock widget 249-4, labeled “Clock;”        -   Icon 542 for workout support module 242, labeled “Workout            Support;”        -   Icon 544 for notes module 253, labeled “Notes;” and        -   Icon 546 for a settings application or module, labeled            “Settings,” which provides access to settings for device 200            and its various applications 236.

It should be noted that the icon labels illustrated in FIG. 5A aremerely exemplary. For example, icon 522 for video and music playermodule 252 are labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 5B illustrates an exemplary user interface on a device (e.g.,device 400, FIG. 4 ) with a touch-sensitive surface 551 (e.g., a tabletor touchpad 455, FIG. 4 ) that is separate from the display 550 (e.g.,touch screen display 212). Device 400 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 457) fordetecting intensity of contacts on touch-sensitive surface 551 and/orone or more tactile output generators 459 for generating tactile outputsfor a user of device 400.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 212 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 5B. In some embodiments, the touch-sensitive surface(e.g., 551 in FIG. 5B) has a primary axis (e.g., 552 in FIG. 5B) thatcorresponds to a primary axis (e.g., 553 in FIG. 5B) on the display(e.g., 550). In accordance with these embodiments, the device detectscontacts (e.g., 560 and 562 in FIG. 5B) with the touch-sensitive surface551 at locations that correspond to respective locations on the display(e.g., in FIG. 5B, 560 corresponds to 568 and 562 corresponds to 570).In this way, user inputs (e.g., contacts 560 and 562, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,551 in FIG. 5B) are used by the device to manipulate the user interfaceon the display (e.g., 550 in FIG. 5B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 6A illustrates exemplary personal electronic device 600. Device 600includes body 602. In some embodiments, device 600 can include some orall of the features described with respect to devices 200 and 400 (e.g.,FIGS. 2A-4B). In some embodiments, device 600 has touch-sensitivedisplay screen 604, hereafter touch screen 604. Alternatively, or inaddition to touch screen 604, device 600 has a display and atouch-sensitive surface. As with devices 200 and 400, in someembodiments, touch screen 604 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 604 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 600 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 600.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, and InternationalPatent Application Serial No. PCT/US2013/069483, titled “Device, Method,and Graphical User Interface for Transitioning Between Touch Input toDisplay Output Relationships,” filed Nov. 11, 2013, each of which ishereby incorporated by reference in their entirety.

In some embodiments, device 600 has one or more input mechanisms 606 and608. Input mechanisms 606 and 608, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 600 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 600 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 600 to be worn by a user.

FIG. 6B depicts exemplary personal electronic device 600. In someembodiments, device 600 can include some or all of the componentsdescribed with respect to FIGS. 2A, 2B, and 4. Device 600 has bus 612that operatively couples I/O section 614 with one or more computerprocessors 616 and memory 618. I/O section 614 can be connected todisplay 604, which can have touch-sensitive component 622 and,optionally, touch-intensity sensitive component 624. In addition, I/Osection 614 can be connected with communication unit 630 for receivingapplication and operating system data, using Wi-Fi, Bluetooth, nearfield communication (NFC), cellular, and/or other wireless communicationtechniques. Device 600 can include input mechanisms 606 and/or 608.Input mechanism 606 is, optionally, a rotatable input device or adepressible and rotatable input device, for example. Input mechanism 608is, optionally, a button, in some examples.

Input mechanism 608 is, optionally, a microphone, in some examples.Personal electronic device 600 optionally includes various sensors, suchas GPS sensor 632, accelerometer 634, directional sensor 640 (e.g.,compass), gyroscope 636, motion sensor 638, and/or a combinationthereof, all of which can be operatively connected to I/O section 614.

Memory 618 of personal electronic device 600 can be a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors616, for example, can cause the computer processors to perform thetechniques described below, including methods 1200, 1300, 1400, or 1500(FIGS. 12-15 ). The computer-executable instructions can also be storedand/or transported within any non-transitory computer-readable storagemedium for use by or in connection with an instruction execution system,apparatus, or device, such as a computer-based system,processor-containing system, or other system that can fetch theinstructions from the instruction execution system, apparatus, or deviceand execute the instructions. For purposes of this document, a“non-transitory computer-readable storage medium” can be any medium thatcan tangibly contain or store computer-executable instructions for useby or in connection with the instruction execution system, apparatus, ordevice. The non-transitory computer-readable storage medium can include,but is not limited to, magnetic, optical, and/or semiconductor storages.Examples of such storage include magnetic disks, optical discs based onCD, DVD, or Blu-ray technologies, as well as persistent solid-statememory such as flash, solid-state drives, and the like. Personalelectronic device 600 is not limited to the components and configurationof FIG. 6B, but can include other or additional components in multipleconfigurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 200, 400, and/or 600 (FIGS. 2, 4, and 6 ). Forexample, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 455 in FIG. 4 or touch-sensitive surface 551 in FIG. 5B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 212 in FIG. 2A or touch screen 212in FIG. 5A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation) rather than being used todetermine whether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

3. Digital Assistant System

FIG. 7A illustrates a block diagram of digital assistant system 700 inaccordance with various examples. In some examples, digital assistantsystem 700 can be implemented on a standalone computer system. In someexamples, digital assistant system 700 can be distributed acrossmultiple computers. In some examples, some of the modules and functionsof the digital assistant can be divided into a server portion and aclient portion, where the client portion resides on one or more userdevices (e.g., devices 104, 122, 200, 400, or 600) and communicates withthe server portion (e.g., server system 108) through one or morenetworks, e.g., as shown in FIG. 1 . In some examples, digital assistantsystem 700 can be an implementation of server system 108 (and/or DAserver 106) shown in FIG. 1 . It should be noted that digital assistantsystem 700 is only one example of a digital assistant system, and thatdigital assistant system 700 optionally has more or fewer componentsthan shown, optionally combines two or more components, or optionallyhas a different configuration or arrangement of the components. Thevarious components shown in FIG. 7A are, optionally, implemented inhardware, software instructions for execution by one or more processors,firmware, including one or more signal processing and/or applicationspecific integrated circuits, or a combination thereof.

Digital assistant system 700 can include memory 702, one or moreprocessors 704, input/output (I/O) interface 706, and networkcommunications interface 708. These components can communicate with oneanother over one or more communication buses or signal lines 710.

In some examples, memory 702 can include a non-transitorycomputer-readable medium, such as high-speed random access memory and/ora non-volatile computer-readable storage medium (e.g., one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices).

In some examples, I/O interface 706 can couple input/output devices 716of digital assistant system 700, such as displays, keyboards, touchscreens, and microphones, to user interface module 722. I/O interface706, in conjunction with user interface module 722, can receive userinputs (e.g., voice input, keyboard inputs, touch inputs, etc.) andprocesses them accordingly. In some examples, e.g., when the digitalassistant is implemented on a standalone user device, digital assistantsystem 700 can include any of the components and I/O communicationinterfaces described with respect to devices 200, 400, or 600 in FIGS.2A, 4, 6A-B, respectively. In some examples, digital assistant system700 can represent the server portion of a digital assistantimplementation, and can interact with the user through a client-sideportion residing on a user device (e.g., devices 104, 200, 400, or 600).

In some examples, the network communications interface 708 can includewired communication port(s) 712 and/or wireless transmission andreception circuitry 714. The wired communication port(s) can receive andsend communication signals via one or more wired interfaces, e.g.,Ethernet, Universal Serial Bus (USB), FIREWIRE, etc. The wirelesscircuitry 714 can receive and send RF signals and/or optical signalsfrom/to communications networks and other communications devices. Thewireless communications can use any of a plurality of communicationsstandards, protocols, and technologies, such as GSM, EDGE, CDMA, TDMA,Bluetooth, Wi-Fi, VoIP, Wi-MAX, or any other suitable communicationprotocol. Network communications interface 708 can enable communicationbetween digital assistant system 700 with networks, such as theInternet, an intranet, and/or a wireless network, such as a cellulartelephone network, a wireless local area network (LAN), and/or ametropolitan area network (MAN), and other devices.

In some examples, memory 702, or the computer-readable storage media ofmemory 702, can store programs, modules, instructions, and datastructures including all or a subset of: operating system 718,communications module 720, user interface module 722, one or moreapplications 724, and digital assistant module 726. In particular,memory 702, or the computer-readable storage media of memory 702, canstore instructions for performing methods 1200, 1300, 1400, or 1500,described below. One or more processors 704 can execute these programs,modules, and instructions, and reads/writes from/to the data structures.

Operating system 718 (e.g., Darwin, RTXC, LINUX, UNIX, iOS, OS X,WINDOWS, or an embedded operating system such as VxWorks) can includevarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communications between varioushardware, firmware, and software components.

Communications module 720 can facilitate communications between digitalassistant system 700 with other devices over network communicationsinterface 708. For example, communications module 720 can communicatewith RF circuitry 208 of electronic devices such as devices 200, 400,and 600 shown in FIGS. 2A, 4, 6A-B, respectively. Communications module720 can also include various components for handling data received bywireless circuitry 714 and/or wired communications port 712.

User interface module 722 can receive commands and/or inputs from a uservia I/O interface 706 (e.g., from a keyboard, touch screen, pointingdevice, controller, and/or microphone), and generate user interfaceobjects on a display. User interface module 722 can also prepare anddeliver outputs (e.g., speech, sound, animation, text, icons,vibrations, haptic feedback, light, etc.) to the user via the I/Ointerface 706 (e.g., through displays, audio channels, speakers,touch-pads, etc.).

Applications 724 can include programs and/or modules that are configuredto be executed by one or more processors 704. For example, if thedigital assistant system is implemented on a standalone user device,applications 724 can include user applications, such as games, acalendar application, a navigation application, or an email application.If digital assistant system 700 is implemented on a server, applications724 can include resource management applications, diagnosticapplications, or scheduling applications, for example.

Memory 702 can also store digital assistant module 726 (or the serverportion of a digital assistant). In some examples, digital assistantmodule 726 can include the following sub-modules, or a subset orsuperset thereof: input/output processing module 728, speech-to-text(STT) processing module 730, natural language processing module 732,dialogue flow processing module 734, task flow processing module 736,service processing module 738, and speech synthesis module 740. Each ofthese modules can have access to one or more of the following systems ordata and models of the digital assistant module 726, or a subset orsuperset thereof: ontology 760, vocabulary index 744, user data 748,task flow models 754, service models 756, and ASR systems.

In some examples, using the processing modules, data, and modelsimplemented in digital assistant module 726, the digital assistant canperform at least some of the following: converting speech input intotext; identifying a user's intent expressed in a natural language inputreceived from the user; actively eliciting and obtaining informationneeded to fully infer the user's intent (e.g., by disambiguating words,games, intentions, etc.); determining the task flow for fulfilling theinferred intent; and executing the task flow to fulfill the inferredintent.

In some examples, as shown in FIG. 7B, I/O processing module 728 caninteract with the user through I/O devices 716 in FIG. 7A or with a userdevice (e.g., devices 104, 200, 400, or 600) through networkcommunications interface 708 in FIG. 7A to obtain user input (e.g., aspeech input) and to provide responses (e.g., as speech outputs) to theuser input. I/O processing module 728 can optionally obtain contextualinformation associated with the user input from the user device, alongwith or shortly after the receipt of the user input. The contextualinformation can include user-specific data, vocabulary, and/orpreferences relevant to the user input. In some examples, the contextualinformation also includes software and hardware states of the userdevice at the time the user request is received, and/or informationrelated to the surrounding environment of the user at the time that theuser request was received. In some examples, I/O processing module 728can also send follow-up questions to, and receive answers from, the userregarding the user request. When a user request is received by I/Oprocessing module 728 and the user request can include speech input, I/Oprocessing module 728 can forward the speech input to STT processingmodule 730 (or speech recognizer) for speech-to-text conversions.

STT processing module 730 can include one or more ASR systems. The oneor more ASR systems can process the speech input that is receivedthrough I/O processing module 728 to produce a recognition result. EachASR system can include a front-end speech pre-processor. The front-endspeech pre-processor can extract representative features from the speechinput. For example, the front-end speech pre-processor can perform aFourier transform on the speech input to extract spectral features thatcharacterize the speech input as a sequence of representativemulti-dimensional vectors. Further, each ASR system can include one ormore speech recognition models (e.g., acoustic models and/or languagemodels) and can implement one or more speech recognition engines.Examples of speech recognition models can include Hidden Markov Models,Gaussian-Mixture Models, Deep Neural Network Models, n-gram languagemodels, and other statistical models. Examples of speech recognitionengines can include the dynamic time warping based engines and weightedfinite-state transducers (WFST) based engines. The one or more speechrecognition models and the one or more speech recognition engines can beused to process the extracted representative features of the front-endspeech pre-processor to produce intermediate recognitions results (e.g.,phonemes, phonemic strings, and sub-words), and ultimately, textrecognition results (e.g., words, word strings, or sequence of tokens).In some examples, the speech input can be processed at least partiallyby a third-party service or on the user's device (e.g., device 104, 200,400, or 600) to produce the recognition result. Once STT processingmodule 730 produces recognition results containing a text string (e.g.,words, or sequence of words, or sequence of tokens), the recognitionresult can be passed to natural language processing module 732 forintent deduction.

More details on the speech-to-text processing are described in U.S.Utility application Ser. No. 13/236,942 for “Consolidating SpeechRecognition Results,” filed on Sep. 20, 2011, the entire disclosure ofwhich is incorporated herein by reference.

In some examples, STT processing module 730 can include and/or access avocabulary of recognizable words via phonetic alphabet conversion module731. Each vocabulary word can be associated with one or more candidatepronunciations of the word represented in a speech recognition phoneticalphabet. In particular, the vocabulary of recognizable words caninclude a word that is associated with a plurality of candidatepronunciations. For example, the vocabulary optionally includes the word“tomato” that is associated with the candidate pronunciations of /

/and /

/. Further, vocabulary words can be associated with custom candidatepronunciations that are based on previous speech inputs from the user.Such custom candidate pronunciations can be stored in STT processingmodule 730 and can be associated with a particular user via the user'sprofile on the device. In some examples, the candidate pronunciationsfor words can be determined based on the spelling of the word and one ormore linguistic and/or phonetic rules. In some examples, the candidatepronunciations can be manually generated, e.g., based on known canonicalpronunciations.

In some examples, the candidate pronunciations can be ranked based onthe commonness of the candidate pronunciation. For example, thecandidate pronunciation /

/ can be ranked higher than /

/ because the former is a more commonly used pronunciation (e.g., amongall users, for users in a particular geographical region, or for anyother appropriate subset of users). In some examples, candidatepronunciations can be ranked based on whether the candidatepronunciation is a custom candidate pronunciation associated with theuser. For example, custom candidate pronunciations can be ranked higherthan canonical candidate pronunciations. This can be useful forrecognizing proper nouns having a unique pronunciation that deviatesfrom canonical pronunciation. In some examples, candidate pronunciationscan be associated with one or more speech characteristics, such asgeographic origin, nationality, or ethnicity. For example, the candidatepronunciation /

/ can be associated with the United States, whereas the candidatepronunciation /

/can be associated with Great Britain. Further, the rank of thecandidate pronunciation can be based on one or more characteristics(e.g., geographic origin, nationality, ethnicity, etc.) of the userstored in the user's profile on the device. For example, it can bedetermined from the user's profile that the user is associated with theUnited States. Based on the user being associated with the UnitedStates, the candidate pronunciation /

/ (associated with the United States) can be ranked higher than thecandidate pronunciation /

/ (associated with Great Britain). In some examples, one of the rankedcandidate pronunciations can be selected as a predicted pronunciation(e.g., the most likely pronunciation).

When a speech input is received, STT processing module 730 can be usedto determine the phonemes corresponding to the speech input (e.g., usingan acoustic model), and then attempt to determine words that match thephonemes (e.g., using a language model). For example, if STT processingmodule 730 can first identify the sequence of phonemes /

/corresponding to a portion of the speech input, it can then determine,based on vocabulary index 744, that this sequence corresponds to theword “tomato.”

In some examples, STT processing module 730 can use approximate matchingtechniques to determine words in an utterance. Thus, for example, theSTT processing module 730 can determine that the sequence of phonemes /

/ corresponds to the word “tomato,” even if that particular sequence ofphonemes is not one of the candidate sequence of phonemes for that word.

Natural language processing module 732 (“natural language processor”) ofthe digital assistant can take the sequence of words or tokens (“tokensequence”) generated by STT processing module 730, and attempt toassociate the token sequence with one or more “actionable intents”recognized by the digital assistant. An “actionable intent” canrepresent a task that can be performed by the digital assistant, and canhave an associated task flow implemented in task flow models 754. Theassociated task flow can be a series of programmed actions and stepsthat the digital assistant takes in order to perform the task. The scopeof a digital assistant's capabilities can be dependent on the number andvariety of task flows that have been implemented and stored in task flowmodels 754, or in other words, on the number and variety of “actionableintents” that the digital assistant recognizes. The effectiveness of thedigital assistant, however, can also be dependent on the assistant'sability to infer the correct “actionable intent(s)” from the userrequest expressed in natural language.

In some examples, in addition to the sequence of words or tokensobtained from STT processing module 730, natural language processingmodule 732 can also receive contextual information associated with theuser request, e.g., from I/O processing module 728. The natural languageprocessing module 732 can optionally use the contextual information toclarify, supplement, and/or further define the information contained inthe token sequence received from STT processing module 730. Thecontextual information can include, for example, user preferences,hardware, and/or software states of the user device, sensor informationcollected before, during, or shortly after the user request, priorinteractions (e.g., dialogue) between the digital assistant and theuser, and the like. As described herein, contextual information can bedynamic, and can change with time, location, content of the dialogue,and other factors.

In some examples, the natural language processing can be based on, e.g.,ontology 760. Ontology 760 can be a hierarchical structure containingmany nodes, each node representing either an “actionable intent” or a“property” relevant to one or more of the “actionable intents” or other“properties.” As noted above, an “actionable intent” can represent atask that the digital assistant is capable of performing, i.e., it is“actionable” or can be acted on. A “property” can represent a parameterassociated with an actionable intent or a sub-aspect of anotherproperty. A linkage between an actionable intent node and a propertynode in ontology 760 can define how a parameter represented by theproperty node pertains to the task represented by the actionable intentnode.

In some examples, ontology 760 can be made up of actionable intent nodesand property nodes. Within ontology 760, each actionable intent node canbe linked to one or more property nodes either directly or through oneor more intermediate property nodes. Similarly, each property node canbe linked to one or more actionable intent nodes either directly orthrough one or more intermediate property nodes. For example, as shownin FIG. 7C, ontology 760 can include a “restaurant reservation” node(i.e., an actionable intent node). Property nodes “restaurant,”“date/time” (for the reservation), and “party size” can each be directlylinked to the actionable intent node (i.e., the “restaurant reservation”node).

In addition, property nodes “cuisine,” “price range,” “phone number,”and “location” can be sub-nodes of the property node “restaurant,” andcan each be linked to the “restaurant reservation” node (i.e., theactionable intent node) through the intermediate property node“restaurant.” For another example, as shown in FIG. 7C, ontology 760 canalso include a “set reminder” node (i.e., another actionable intentnode). Property nodes “date/time” (for setting the reminder) and“subject” (for the reminder) can each be linked to the “set reminder”node. Since the property “date/time” can be relevant to both the task ofmaking a restaurant reservation and the task of setting a reminder, theproperty node “date/time” can be linked to both the “restaurantreservation” node and the “set reminder” node in ontology 760.

An actionable intent node, along with its linked concept nodes, can bedescribed as a “domain.” In the present discussion, each domain can beassociated with a respective actionable intent, and refers to the groupof nodes (and the relationships there between) associated with theparticular actionable intent. For example, ontology 760 shown in FIG. 7Ccan include an example of restaurant reservation domain 762 and anexample of reminder domain 764 within ontology 760. The restaurantreservation domain includes the actionable intent node “restaurantreservation,” property nodes “restaurant,” “date/time,” and “partysize,” and sub-property nodes “cuisine,” “price range,” “phone number,”and “location.” Reminder domain 764 can include the actionable intentnode “set reminder,” and property nodes “subject” and “date/time.” Insome examples, ontology 760 can be made up of many domains. Each domaincan share one or more property nodes with one or more other domains. Forexample, the “date/time” property node can be associated with manydifferent domains (e.g., a scheduling domain, a travel reservationdomain, a movie ticket domain, etc.), in addition to restaurantreservation domain 762 and reminder domain 764.

While FIG. 7C illustrates two example domains within ontology 760, otherdomains can include, for example, “find a movie,” “initiate a phonecall,” “find directions,” “schedule a meeting,” “send a message,” and“provide an answer to a question,” “read a list,” “providing navigationinstructions,” “provide instructions for a task” and so on. A “send amessage” domain can be associated with a “send a message” actionableintent node, and optionally further includes property nodes such as“recipient(s),” “message type,” and “message body.” The property node“recipient” can be further defined, for example, by the sub-propertynodes such as “recipient name” and “message address.”

In some examples, ontology 760 can include all the domains (and henceactionable intents) that the digital assistant is capable ofunderstanding and acting upon. In some examples, ontology 760 can bemodified, such as by adding or removing entire domains or nodes, or bymodifying relationships between the nodes within the ontology 760.

In some examples, nodes associated with multiple related actionableintents can be clustered under a “super domain” in ontology 760. Forexample, a “travel” super-domain can include a cluster of property nodesand actionable intent nodes related to travel. The actionable intentnodes related to travel can include “airline reservation,” “hotelreservation,” “car rental,” “get directions,” “find points of interest,”and so on. The actionable intent nodes under the same super domain(e.g., the “travel” super domain) can have many property nodes incommon. For example, the actionable intent nodes for “airlinereservation,” “hotel reservation,” “car rental,” “get directions,” and“find points of interest” can share one or more of the property nodes“start location,” “destination,” “departure date/time,” “arrivaldate/time,” and “party size.”

In some examples, each node in ontology 760 can be associated with a setof words and/or phrases that are relevant to the property or actionableintent represented by the node. The respective set of words and/orphrases associated with each node can be the so-called “vocabulary”associated with the node. The respective set of words and/or phrasesassociated with each node can be stored in vocabulary index 744 inassociation with the property or actionable intent represented by thenode. For example, returning to FIG. 7B, the vocabulary associated withthe node for the property of “restaurant” can include words such as“food,” “drinks,” “cuisine,” “hungry,” “eat,” “pizza,” “fast food,”“meal,” and so on. For another example, the vocabulary associated withthe node for the actionable intent of “initiate a phone call” caninclude words and phrases such as “call,” “phone,” “dial,” “ring,” “callthis number,” “make a call to,” and so on. The vocabulary index 744 canoptionally include words and phrases in different languages.

Natural language processing module 732 can receive the token sequence(e.g., a text string) from STT processing module 730, and determine whatnodes are implicated by the words in the token sequence. In someexamples, if a word or phrase in the token sequence is found to beassociated with one or more nodes in ontology 760 (via vocabulary index744), the word or phrase can “trigger” or “activate” those nodes. Basedon the quantity and/or relative importance of the activated nodes,natural language processing module 732 can select one of the actionableintents as the task that the user intended the digital assistant toperform. In some examples, the domain that has the most “triggered”nodes can be selected. In some examples, the domain having the highestconfidence value (e.g., based on the relative importance of its varioustriggered nodes) can be selected. In some examples, the domain can beselected based on a combination of the number and the importance of thetriggered nodes. In some examples, additional factors are considered inselecting the node as well, such as whether the digital assistant haspreviously correctly interpreted a similar request from a user.

User data 748 can include user-specific information, such asuser-specific vocabulary, user preferences, user address, user's defaultand secondary languages, user's contact list, and other short-term orlong-term information for each user. In some examples, natural languageprocessing module 732 can use the user-specific information tosupplement the information contained in the user input to further definethe user intent. For example, for a user request “invite my friends tomy birthday party,” natural language processing module 732 can be ableto access user data 748 to determine who the “friends” are and when andwhere the “birthday party” would be held, rather than requiring the userto provide such information explicitly in his/her request.

Other details of searching an ontology based on a token string isdescribed in U.S. Utility application Ser. No. 12/341,743 for “Methodand Apparatus for Searching Using An Active Ontology,” filed Dec. 22,2008, the entire disclosure of which is incorporated herein byreference.

In some examples, once natural language processing module 732 identifiesan actionable intent (or domain) based on the user request, naturallanguage processing module 732 can generate a structured query torepresent the identified actionable intent. In some examples, thestructured query can include parameters for one or more nodes within thedomain for the actionable intent, and at least some of the parametersare populated with the specific information and requirements specifiedin the user request. For example, the user says “Make me a dinnerreservation at a sushi place at 7.” In this case, natural languageprocessing module 732 can be able to correctly identify the actionableintent to be “restaurant reservation” based on the user input. Accordingto the ontology, a structured query for a “restaurant reservation”domain optionally includes parameters such as {Cuisine}, {Time}, {Date},{Party Size}, and the like. In some examples, based on the speech inputand the text derived from the speech input using STT processing module730, natural language processing module 732 can generate a partialstructured query for the restaurant reservation domain, where thepartial structured query includes the parameters {Cuisine=“Sushi”} and{Time=“7 pm”}. However, in this example, the user's utterance containsinsufficient information to complete the structured query associatedwith the domain. Therefore, other necessary parameters such as {PartySize} and {Date} are, optionally, not specified in the structured querybased on the information currently available. In some examples, naturallanguage processing module 732 can populate some parameters of thestructured query with received contextual information. For example, insome examples, if the user requested a sushi restaurant “near me,”natural language processing module 732 can populate a {location}parameter in the structured query with GPS coordinates from the userdevice.

In some examples, natural language processing module 732 can pass thegenerated structured query (including any completed parameters) to taskflow processing module 736 (“task flow processor”). Task flow processingmodule 736 can be configured to receive the structured query fromnatural language processing module 732, complete the structured query,if necessary, and perform the actions required to “complete” the user'sultimate request. In some examples, the various procedures necessary tocomplete these tasks can be provided in task flow models 754. In someexamples, task flow models 754 can include procedures for obtainingadditional information from the user and task flows for performingactions associated with the actionable intent.

As described above, in order to complete a structured query, task flowprocessing module 736 optionally need to initiate additional dialoguewith the user in order to obtain additional information, and/ordisambiguate potentially ambiguous utterances. When such interactionsare necessary, task flow processing module 736 can invoke dialogue flowprocessing module 734 to engage in a dialogue with the user. In someexamples, dialogue flow processing module 734 can determine how (and/orwhen) to ask the user for the additional information and receives andprocesses the user responses. The questions can be provided to andanswers can be received from the users through I/O processing module728. In some examples, dialogue flow processing module 734 can presentdialogue output to the user via audio and/or visual output, and receivesinput from the user via spoken or physical (e.g., clicking) responses.Continuing with the example above, when task flow processing module 736invokes dialogue flow processing module 734 to determine the “partysize” and “date” information for the structured query associated withthe domain “restaurant reservation,” dialogue flow processing module 734can generate questions such as “For how many people?” and “On whichday?” to pass to the user. Once answers are received from the user,dialogue flow processing module 734 can then populate the structuredquery with the missing information, or pass the information to task flowprocessing module 736 to complete the missing information from thestructured query.

Once task flow processing module 736 has completed the structured queryfor an actionable intent, task flow processing module 736 can proceed toperform the ultimate task associated with the actionable intent.Accordingly, task flow processing module 736 can execute the steps andinstructions in the task flow model according to the specific parameterscontained in the structured query. For example, the task flow model forthe actionable intent of “restaurant reservation” can include steps andinstructions for contacting a restaurant and actually requesting areservation for a particular party size at a particular time. Forexample, using a structured query such as: {restaurant reservation,restaurant=ABC Café, date=3/12/2012, time=7 pm, party size=5}, task flowprocessing module 736 can perform the steps of: (1) logging onto aserver of the ABC Café or a restaurant reservation system such asOPENTABLE®, (2) entering the date, time, and party size information in aform on the website, (3) submitting the form, and (4) making a calendarentry for the reservation in the user's calendar.

In some examples, task flow processing module 736 can employ theassistance of service processing module 738 (“service processingmodule”) to complete a task requested in the user input or to provide aninformational answer requested in the user input. For example, serviceprocessing module 738 can act on behalf of task flow processing module736 to make a phone call, set a calendar entry, invoke a map search,invoke or interact with other user applications installed on the userdevice, and invoke or interact with third-party services (e.g., arestaurant reservation portal, a social networking website, a bankingportal, etc.). In some examples, the protocols and applicationprogramming interfaces (API) required by each service can be specifiedby a respective service model among service models 756. Serviceprocessing module 738 can access the appropriate service model for aservice and generate requests for the service in accordance with theprotocols and APIs required by the service according to the servicemodel.

For example, if a restaurant has enabled an online reservation service,the restaurant can submit a service model specifying the necessaryparameters for making a reservation and the APIs for communicating thevalues of the necessary parameter to the online reservation service.When requested by task flow processing module 736, service processingmodule 738 can establish a network connection with the onlinereservation service using the web address stored in the service model,and send the necessary parameters of the reservation (e.g., time, date,party size) to the online reservation interface in a format according tothe API of the online reservation service.

In some examples, natural language processing module 732, dialogue flowprocessing module 734, and task flow processing module 736 can be usedcollectively and iteratively to infer and define the user's intent,obtain information to further clarify and refine the user intent, andfinally generate a response (i.e., an output to the user, or thecompletion of a task) to fulfill the user's intent. The generatedresponse can be a dialogue response to the speech input that at leastpartially fulfills the user's intent. Further, in some examples, thegenerated response can be output as a speech output. In these examples,the generated response can be sent to speech synthesis module 740 (e.g.,speech synthesizer) where it can be processed to synthesize the dialogueresponse in speech form. In yet other examples, the generated responsecan be data content relevant to satisfying a user request in the speechinput.

Speech synthesis module 740 can be configured to synthesize speechoutputs for presentation to the user. Speech synthesis module 740synthesizes speech outputs based on text provided by the digitalassistant. For example, the generated dialogue response can be in theform of a text string. Speech synthesis module 740 can convert the textstring to an audible speech output. Speech synthesis module 740 can useany appropriate speech synthesis technique in order to generate speechoutputs from text, including, but not limited, to concatenativesynthesis, unit selection synthesis, diphone synthesis, domain-specificsynthesis, formant synthesis, articulatory synthesis, hidden Markovmodel (HMM) based synthesis, and sinewave synthesis. In some examples,speech synthesis module 740 can be configured to synthesize individualwords based on phonemic strings corresponding to the words. For example,a phonemic string can be associated with a word in the generateddialogue response. The phonemic string can be stored in metadataassociated with the word. Speech synthesis model 740 can be configuredto directly process the phonemic string in the metadata to synthesizethe word in speech form.

In some examples, instead of (or in addition to) using speech synthesismodule 740, speech synthesis can be performed on a remote device (e.g.,the server system 108), and the synthesized speech can be sent to theuser device for output to the user. For example, this can occur in someimplementations where outputs for a digital assistant are generated at aserver system. And because server systems generally have more processingpower or resources than a user device, it can be possible to obtainhigher quality speech outputs than would be practical with client-sidesynthesis.

Additional details on digital assistants can be found in the U.S.Utility application Ser. No. 12/987,982, entitled “Intelligent AutomatedAssistant,” filed Jan. 10, 2011, and U.S. Utility application Ser. No.13/251,088, entitled “Generating and Processing Task Items ThatRepresent Tasks to Perform,” filed Sep. 30, 2011, the entire disclosuresof which are incorporated herein by reference.

Attention is now directed towards embodiments of techniques andassociated user interfaces (“UP”) for triggering (e.g., initiating) avirtual assistant that are, optionally, implemented on an electronicdevice with a display and a touch-sensitive surface.

4. Exemplary Techniques for Triggering a Virtual Assistant

FIGS. 8A-8C illustrate exemplary techniques for triggering a virtualassistant based on whether input at an electronic device meets apredetermined condition, in accordance with some embodiments. Thesefigures are also used to illustrate the processes described below,including the processes in FIG. 12 .

FIG. 8A illustrates electronic device 800 of user 802. Device 800 is oneof devices 104, 122, 200, 400, 600, and 1700 (FIGS. 1, 2, 4, 6, and 17 )in some embodiments. Device 800 has touch screen 804. In the illustrated(e.g., lowered) position, touch screen 804 is powered off to conservebattery usage.

FIG. 8B illustrates user 802 lifting electronic device 800 into a raisedposition for viewing. In response to the movement, device 800 powers ontouch screen 804 to present a user interface. Techniques for determiningdevice movement such as the lifting movement seen in FIGS. 8A and 8B arefurther described with reference to FIG. 12 , below.

In accordance with touch screen 804 powering on, device 800 also beginsto sample audio input through its microphone to listen for spoken inputfrom user 802. FIG. 8C illustrates user 802 providing spokeninstructions 810 while device 800 is sampling audio input. As device 800detects spoken instruction 810 while sampling audio input, the devicedetermines whether the sampled audio input contains a phrase fortriggering a virtual assistant service. If device 800 determines thatthe sampled input contains a spoken trigger for triggering a virtualassistant, device 800 triggers the virtual assistant. If device 800determines that the sampled audio input does not contain the spokentrigger, it optionally continues to sample audio input for the spokentrigger for a limited time.

In the illustrated example, the spoken trigger is the phrase of “HeySiri.” Thus, spoken instruction 810, when sampled by device 800, causesdevice 800 to trigger a virtual assistant service. However, instruction810 does not contain additional language representing a user request,beyond the trigger phrase. Thus, device 800 awaits further spoken inputupon trigger the virtual assistant service by continuing to sample audioinput. While awaiting additional input, device 800 optionally displaysindication 812 prompting user 802 for further instructions.

In this way, device 800 activates the microphone, associated circuitry,and corresponding software processes for sampling audio input for avirtual assistant based on whether the device has detected a particularusage condition. This technique allows device 800 to disable certainelectronic circuitry (e.g., microphone circuitry) and/or reduceexecution of computer instructions (e.g., an associated processor powerconsumption) at times when a user is less likely to be providing active,cognitive input to the device—such as when the device is lowered and itsdisplay is powered off—thereby reducing overall power consumption by thedevice. Restated, the technical benefit of battery conservation isachieved through the notion that a user is less likely to provide spokeninput while the device is outside certain usage conditions, in someembodiments.

FIGS. 9A-9D illustrate exemplary techniques for triggering a virtualassistant session in accordance with some embodiments. These figures arealso used to illustrate the processes described below, including theprocesses in FIG. 13 .

FIG. 9A illustrates electronic device 900 of user 902. Device 900 is oneof devices 104, 122, 200, 400, 600, and 1600 (FIGS. 1, 2, 4, 6, and 16 )in some embodiments. Device 900 has touch screen 904. Touch screen 904is displaying notification 906 notifying user 902 of an incoming messagejust received by device 900. The display of notification 906 istriggered by one or more software events associated with the incomingmessage. In accordance with detecting one or more relevant softwareevents, device 900 begins to sample audio input via its microphone toidentify spoken input. Techniques for determining relevant softwareevents such as message notifications as seen in FIGS. 9A and 9B arefurther described with reference to FIG. 13 , below.

FIG. 9B illustrates user 902 providing spoken instructions 910 whiledevice 900 is sampling audio input. When device 900 detects spokeninstruction 910 in accordance with its sampling of audio input, thedevice determines whether the sampled input contains a spoken triggerfor a virtual assistant. In the illustrated example, the spoken triggeris the phrase of “Hey Siri.” If device 900 determines that the sampledinput contains a spoken trigger for triggering a virtual assistant,device 900 triggers the virtual assistant. If device 900 determines thatthe sampled audio input does not contain the spoken trigger, itoptionally continues to sample audio input for the spoken trigger for alimited time.

In the illustrated example, spoken instructions 910 contains both aspoken trigger (e.g., “hey Siri”) and natural language input (e.g.,“tell the sender I can't chat right now”) that the virtual assistant canoperationalize into computing tasks. For example, the task is to send abrief reply to the sender of incoming message 912. Turning to FIG. 9C,responsive to the sampling of audio input containing instructions 910,electronic device 900 initiates and transmits message 916 to sender 918of incoming message 912, informing the sender that user 902 is currentlyunavailable.

This technique of powering-on the microphone of device 900 in accordancewith software events detected by the device, as illustrated by FIGS.9A-9C, allows electronic device 900 to disable certain electroniccircuitry (e.g., microphone circuitry) and/or reduce execution ofcomputer instructions (e.g., an associated processor power consumption)at times when a user is less likely to be providing active, cognitiveinput to the device, thereby reducing overall power consumption by thedevice. Restated, the technical benefit of battery conservation isachieved through the notion that a user is less likely to provide spokeninput while the device is idle from software events that cause output tothe user, in some embodiments.

FIGS. 10A-10D illustrate exemplary techniques for triggering a virtualassistant session in accordance with some embodiments. These figures arealso used to illustrate the processes described below, including theprocesses in FIG. 14 .

FIG. 10A illustrates electronic device 1000 of user 1002. Device 1000 isone of 104, 122, 200, 400, 600, and 1700 (FIGS. 1, 2, 4, 6, and 17 ) insome embodiments. Device 1000 has touch screen 1004. In its illustratedposition (e.g., lowered), touch screen 1004 is powered off to conservethe battery life of device 1000. FIG. 10B illustrates user 1002 liftingelectronic device 1000 into a raised position for viewing. In responseto the movement, device 1000 begins to sample audio input for spokeninput from user 1002. In some embodiments, device 1000 begins thissampling of audio input even though touch screen 1004 remains off. Insome embodiments, device 1000 begins this sampling of audio inputregardless of whether touch screen 1004 is on or off.

FIG. 10C illustrates user 1002 providing spoken instructions 1010 whiledevice 1000 is sampling audio input with touch screen 1004 off. Whendevice 1000 detects spoken instruction 1010 in accordance of itssampling of audio input, the device determines whether the sampled inputcontains a spoken trigger for a virtual assistant. In the illustratedexample, the spoken trigger is the phrase of “Hey Siri.” If device 1000determines that the sampled input contains a spoken trigger fortriggering a virtual assistant, device 1000 triggers the virtualassistant without powering on touch screen 1004, if the screen ispowered off. If device 1000 determines that the sampled audio input doesnot contain the spoken trigger, it optionally continues to sample audioinput for the spoken trigger for some time, as further described withreference to FIG. 14 , below.

In the illustrated example of FIG. 10C, the sampled audio input containsa spoken trigger (e.g., “hey Siri”) and a natural language input (e.g.,“download my e-mail”) that the virtual assistant can operationalize intotasks. In some embodiments, device 1000 provides output (e.g., hapticand/or audio output) acknowledging the received spoken input. In someembodiments, the acknowledgement output is provided without turning ontouch screen 1004.

Turning to FIG. 10D, responsive to spoken instructions 1010, device 1000initiates the requested task of downloading e-mail. In some embodiments,the task is performed while touch screen 1004 remains powered off. Insome embodiments, device 1000 provides output (e.g., haptic and/or audiooutput) indicating to the user that the spoken input is being performedand/or has been performed. In some embodiments, the output is providedwithout turning on touch screen 1004.

This technique of powering-on a device's microphone to process a user'sspoken input under some usage conditions while the touch screen remainsoff, described with reference to FIGS. 10A-10D, permits reductions inoverall power consumption by device 1000, while maintaining the device'sability to process a user's spoken input. Restated, the technicalbenefit of battery conservation is achieved through efficient controlson the activation of the display on a display-equipped device, in someembodiments.

FIGS. 11A-11C illustrate exemplary techniques for triggering a virtualassistant session in accordance with some embodiments. These figures arealso used to illustrate the processes described below, including theprocesses in FIG. 15 .

FIG. 11A illustrates electronic device 1100 of user 1102. Device 1100 isone of 104, 122, 200, 400, 600, and 1800 (FIGS. 1, 2, 4, 6, and 18 ) insome embodiments. Device 1100 has touch screen 1104. Touch screen 1104is displaying indication 1106 indicating that a virtual assistantsession is active and is awaiting the user's spoken instructions. Whilethe virtual assistant session is active, a microphone of device 1100 issampling audio input for user instructions. Other user interfaces (notshown) optionally also indicate that a virtual assistant session isactive, such as a virtual assistant transcript listing the previous userinputs and virtual assistant responses. Touch screen 1104 also displaysincludes cancel affordance 1108 for ending the virtual assistantsession.

As seen in FIG. 11B, responsive to detecting user selection of cancelaffordance 1108, device 1100 reports to the user that the virtualassistant session has ended by replacing virtual assistant indication1106 with a non-virtual assistant user interface. In the illustratedexample, device 1100 displays digital clock face 1110. In someembodiments (not expressly illustrated in FIG. 11B), device 1100 powersoff touch screen 1104 in acknowledging the user's cancellation of thevirtual assistant session.

In some embodiments, however, even as device 1100 indicates to the userthat the virtual assistant session has ended, its microphone continuesto sample audio input for the user's spoken instructions for some time.In some embodiments, the on-going audio sampling occurs for apredetermined amount of time (e.g., eight seconds). In some embodiments,the on-going audio sampling occurs until an additional user input isreceived, such as a touch input on touch screen 1104, activation of anapplication, so forth. Additional techniques for identifying a durationfor which the sampling of audio input continues are described withreference to FIG. 15 , below.

Turning to FIG. 11C, during its on-going sampling of audio input, device1100 triggers the virtual assistant responsive to sampled audio inputthat includes a spoken trigger, such as spoken input 1112 which includesthe phrase “hey Siri.”

This technique of continuing to sample audio input for a time after auser has ended a virtual assistant (as opposed to turning off themicrophone immediately) is beneficial. Consider, for instance, thesituation in which a user's cancellation of the virtual assistant (e.g.,at FIG. 11B) is erroneous, and has the effect of placing the device intoa state where it is would have placed awaiting an intermediate inputsuch as device movement before sampling audio input again. That is, theuser's erroneous cancellation would have precluded the device's abilityto process the user's immediate subsequent spoken input. Under thissituation, the above-described techniques permit the device to respondas if the erroneous user input did not occur.

As another example, consider the situation in which a user'scancellation of the virtual assistant would have delayed the device'sability to process the user's subsequent spoken input by requiring thedevice to power-cycle its microphone and associated circuitry. Theabove-described techniques permit electronic device 1100 to respond tothe user while avoiding the delay caused by power cycle, therebyimproving response times. These benefits impart a higher-quality userexperience to device 1100, and are particularly helpful for portabledevices where design compromises are made between processing power andbattery consumption.

FIGS. 20A-20F illustrate exemplary techniques for handling a user'srequest to a virtual assistant, in accordance with some embodiments.These figures are also used to illustrate the processes described below,including the processes in FIG. 21 .

FIG. 20A illustrates electronic device 2000 of user 2002. Device 2000 isone of 104, 122, 200, 400, 600, and 1900 (FIGS. 1, 2, 4, 6, and 19 ) insome embodiments. Device 2000 has touch screen 2004. As depicted in FIG.20A, device 2000 is displaying a virtual assistant user interface 2006,indicating that it is sampling audio input for user instructions 2010,which instructs the device to initiate a message to a recipient.

Turning to FIG. 20B, device 2000 begins to process spoken instructions2010 to identify computing tasks that can be performed to fulfill theuser's instructions. The amount of time that is required tooperationalize a user's instruction varies under different usagescenarios. For example, a slow data service provider optionally slowsdown the device's response time.

As seen in FIG. 20C, while the virtual assistant is processing theuser's instructions, user 2002 optionally lowers device 2000 into anon-viewing position. In the absence of user input, touch screen 2004turns off after some time to conserve battery power, even as virtualassistant continues to process user instructions 2010, in theillustrated example.

Turning to FIG. 20D, when device 2000 has operationalized the user'sinstructions to a point where output should be displayed to the user,device 200 provides a haptic and/or audible output such that the user isnotified that additional information is now available. For example, inresponse to user instructions 2010, device 2000 optionally displays aconfirmation after it has launched a messaging application and populatedan outgoing message, but before sending the message to the recipient.

As seen in FIG. 20E, alerted by the haptic and/or audible output, user2002 optionally raises device 2000 into viewing position, which powerson touch screen 2004 to show message 2012 addressed to recipient “Jen”and containing message body 2012, both of which correspond to the user'snatural language input 2010.

Although the examples of FIGS. 20A-20E depict a user's instructions tocreate a message, the techniques described are not so limited. Thevirtual assistant of device 2000 optionally uses a haptic and/or audiblealert to inform the user whenever the virtual assistant has obtaineduseful results while the device's screen is off. For instance, device2000 optionally vibrates to alert the user that navigation directionshave been downloaded and are available for viewing. In this way, device2000 optionally relieves the user from having to focus on the devicewhile the user's input is being processed. These techniques also permitdevice 2000 to power down its touch screen momentarily to conservebattery power while its virtual assistant continues to perform tasks.

6. Exemplary Processes for Triggering a Virtual Assistant

FIG. 12 is a flow diagram illustrating method 1200 of triggering avirtual assistant on an electronic device in accordance with someembodiments. Method 1200 is performed at one of devices 104, 200, 400,800, and 1600 (FIGS. 1, 2, 4, 8, and 16 ) in some embodiments. In someembodiments, method 1200 is performed at a device having a touch screen.In some embodiments, method 1200 is performed at a device with aseparate display screen and a touch-sensitive surface. Operations inmethod 1200 are, optionally, combined and/or the order of someoperations is, optionally, changed.

At block 1202, while the electronic device's display is on, the devicedetects user input via an input component of the device. At block 1204,the device determines if the input meets a predetermined condition. Ifthe input meets a predetermined condition, processing proceeds to 1206where the device samples audio input received via its microphone. If theinput does not meet the predetermined condition, processing returns toblock 1202, where the device optionally detects another user input.

In some embodiments, the predetermined condition is that the displayscreen of the device is on. The device determines whether the display ison, for example, by determining whether its backlight is lit.

In some embodiments, the predetermined condition is a movement of thedevice, such as a lifting of the device into a viewing position (as seenin FIGS. 8A and 8B). Whether device movement constitutes a liftingmovement is based on accelerometer readings over time, in someembodiments. Whether device movement constitutes a lifting movement isbased on the smoothness of accelerometer readings over time, in someembodiments. Whether device movement constitutes a lifting movement isbased on sensing minimum period of dwell time (e.g., a period ofrelative non-movement or steadiness), in some embodiments.

In the exemplary lifting movement depicted in FIGS. 8A-8B (as well as inFIGS. 10A-10B), user 802 raises device 800 from its lowered position inFIG. 8A to its raised position in FIG. 8B. This movement includesacceleration over time in one direction (e.g., in the vertical directionalong the y-axis), and a rotational acceleration over time in anotherdirection (e.g., a horizontal rotation about the x-axis), both of whichcan be determined by the acceleration sensors of device 800. Optionally,the smoothness of such a lifting movement can be determined by comparingfluctuations the acceleration sensors' readings over time. Optionally,the lifting movement ends with the user glancing on the device's touchscreen in the raised position. The period of relative steadiness as user802 focuses on the display of device 800 can be determined usingacceleration sensor readings. Device 800 uses at least some of theseaccelerometer readings in determining whether a predetermined conditionfor sampling audio input via microphone is met, in some embodiments.

Additional detail regarding techniques for determining raising gesturesof an electronic device are described in, e.g., U.S. Provisional PatentApplication Ser. No. 62/026,532, titled “Raise Gesture Detection in aDevice,” filed Jul. 18, 2014, the content of which is herebyincorporated by reference. For brevity, the content of the applicationis not repeated here.

In some embodiments, the predetermined condition is activation of aninput device such as a mechanical button, touch-sensitive button,rotatable input device, so forth. In some embodiments, the predeterminedcondition is a touch on touch-sensitive surface or touch screen (such astouch screen 804 shown in FIG. 8A).

Optionally, at block 1204, the device determines whether it is operatingin a predetermined mode where its audio output is muted (e.g., a “do notdisturb”). If the device is operating in such a mode, processing returnsto block 1202, meaning that the device foregoes sampling audio fortriggering a virtual assistant.

In some embodiments, sampling audio at block 1206 involves powering on amicrophone of the device. In some examples, sampling audio involvespowering on additional electronics circuitry to perform signalprocessing. In some examples, sampling audio involves passing audioinput received from the microphone to software recognition algorithmsthat are being executed on one or more processors of the device.

Having sampled audio input at block 1206, the device proceeds to block1208, where it determines whether the sampled audio input comprises aspoken trigger for triggering a virtual assistant. If the sampled audioinput contains the spoken trigger, processing proceeds to block 1210where the device triggers a virtual assistant session (such as bydisplaying user interface 812 shown in FIG. 8C). In some embodiments,the spoken trigger is a predetermined phrase, such as “hey Siri.”

If the sampled audio input does not contain the spoken trigger,processing proceeds to block 1212, where the device determines whetherto continue to sample audio input. If the device is to continue samplingaudio input, processing returns to block 1206 where audio samplingcontinues. If the device is to cease sampling of audio input, processingproceeds to block 1214 where audio sampling is stopped.

In some embodiments, the device ceases to sample audio input after thedevice's display is turned off. In some embodiments, the devices ceasesto sample audio input after sampling for a threshold duration of time,such as a duration of eight seconds. In some embodiments, the deviceceases to sample audio after detecting activation of an input devicesuch as a mechanical button, touch-sensitive button, rotatable inputdevice, so forth. In some embodiments, the device ceases to sample audioafter detecting activation of an input device such as a touch ontouch-sensitive surface or touch screen.

In some embodiments, the device ceases to sample audio input after anintervening input is received, such as a user input to invoke anotherapplication installed on the device. In some embodiments, the deviceceases to sample audio based on an amount of lowering of the deviceduring a time interval, the amount of lowering determined from anaccelerometer of the electronic device. In some embodiment, the deviceceases to sample audio based on smoothness of a lowering of theelectronic device during a time interval, the smoothness of the loweringdetermined from an accelerometer of the device. In some embodiment, thedevice ceases to sample audio input after identifying an audio endpointin the audio input. Exemplary end points include those indicating thatthe received audio input is too low in volume to be near-field speech(as opposed to background noise), unlikely to be human speech, a stop inthe user's spoken input, so forth.

In some embodiments, the device ceases sampling of audio ceases at block1214 by powering off the microphone of the device. In some embodiments,sampling of audio ceases by powering off associated circuitry thatperforms microphone signal processing. In some embodiments, samplingaudio ceases by not processing audio input received from the microphonethrough software recognition algorithms. Optionally, at block 1214, thedevice provides one or more of a haptic, audio, and visual outputindicating the end of the audio sampling.

It should be understood that the particular order in which theoperations in FIG. 12 has been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 1300 and 1500) are also applicable in an analogous manner tomethod 1200 described above with respect to FIG. 12 . For example, it ispossible for the device performing method 1200 to also perform method1500 (FIG. 15 ) for overcoming erroneous user cancellation of thevirtual assistant. For brevity, these details are not repeated here.

FIG. 13 is a flow diagram illustrating method 1300 of triggering avirtual assistant on an electronic device in accordance with someembodiments. Method 1300 is performed at one of devices 104, 200, 400,900, and 1700 (FIGS. 1, 2, 4, 8, and 17 ) in some embodiments. In someembodiments, method 1300 is performed at a device having a touch screen.In some embodiments, method 1300 is performed at a device with aseparate display screen and a touch-sensitive surface. Operations inmethod 1300 are, optionally, combined and/or the order of someoperations is, optionally, changed.

At block 1302, the electronic device detects a software event. At block1304, the device determines whether the software event meets apredetermined condition. If the software event meets the predeterminedcondition, processing proceeds to block 1306, and the device beginssampling audio input received via its microphone. If the software eventdoes not meet the predetermined condition, processing returns to block1302, where the device optionally detects another software event.

In the illustration of FIG. 9A, notification 906 of incoming textmessage 912 meets the predetermined condition for causing device 900 tosample audio input. In some embodiments, the predetermined condition isthat the software event is an operating system event triggered by theoperating system of the device. Exemplary software events triggered bythe operating system includes an alert about a hardware component ofdevice 900, such as an alert that the device has been connected to acomputer via cable. In some embodiments, the predetermined condition isthat the software event is an application-based event triggered by anapplication executing on the device. Exemplary software events triggeredby an application of the device include, calendar reminders, taskreminders, so forth. Exemplary software events that are, optionally,considered to have been triggered by the operating system and/or anapplication or device 900 include clock events such as an alarm or atimer expiration.

In some embodiments, the predetermined condition is that the softwareevent is an event triggered by an external source. Exemplary softwareevents triggered by external sources include incoming calls (e.g.,voice- or video-based, cellular or WiFi-based calls), messages (e.g.,e-mail, text message SMS, multimedia message, iMessage, so forth)calendar invitations, so forth. Exemplary software events triggered byexternal sources also include application-based notifications andalerts, such as alerts indicating the availability of newly availableinformation on a web site or service.

In some embodiments, the predetermined condition is that the softwareevent indicates that a virtual assistant session is active on thedevice.

Optionally, at block 1304, the device determines whether it is operatingin a predetermined mode where its audio output is muted (e.g., a “do notdisturb”). If the device is operating is such a mode, processing returnsto block 1302, meaning that the device foregoes sampling audio fortriggering a virtual assistant.

Optionally, at block 1304, the device determines its display screen ison. The device determines whether the display is on, for example, bydetermining whether its backlight is lit. If the device's display isoff, processing returns to block 1302, meaning that the device foregoessampling audio for triggering a virtual assistant.

Having sampled audio input at block 1306, the device proceeds to block1308, where it determines whether the sampled audio input includes aspoken trigger for triggering a virtual assistant. If the sampled audioinput contains the spoken trigger, processing proceeds to block 1310where the device triggers a virtual assistant session and, optionally,executes tasks based on the user's spoken input (as can been seen in theexemplary illustrations of FIGS. 9B and 9C). In some embodiments, thespoken trigger is a predetermined phrase, such as “hey Siri.”

If the sampled audio input does not contain the spoken trigger,processing proceeds to block 1312, where the device determines whetherto continue to sample audio input. If the device is to continue samplingaudio input, processing returns to block 1306 where audio samplingcontinues. If the device is to cease sampling of audio input, processingproceeds to block 1314 where audio sampling is stopped.

In some embodiments, the device ceases to sample audio input after thedevice's display is turned off. In some embodiments, the devices ceasesto sample audio input after sampling for a threshold duration of time,such as a duration of eight seconds. In some embodiments, the deviceceases to sample audio after detecting activation of an input devicesuch as a mechanical button, touch-sensitive button, rotatable inputdevice, so forth. In some embodiments, the device ceases to sample audioafter detecting activation of an input device such as a touch ontouch-sensitive surface or touch screen.

In some embodiments, the device ceases to sample audio input after anintervening input is received, such as a user input to invoke anotherapplication installed on the device. In some embodiments, the deviceceases to sample audio based on an amount of lowering of the deviceduring a time interval, the amount of lowering determined from anaccelerometer of the electronic device. In some embodiments, the deviceceases to sample audio based on smoothness of a lowering of theelectronic device during a time interval, the smoothness of the loweringdetermined from an accelerometer of the device. In some embodiments, thedevice ceases to sample audio input after identifying an audio endpointin the audio input. Exemplary end points include those indicating thatthe received audio input is too low in volume to be near-field speech(as opposed to background noise), unlikely to be human speech, a stop inthe user's spoken input, so forth.

In some embodiments, the device ceases sampling of audio ceases at block1314 by powering off the microphone of the device. In some embodiments,sampling of audio ceases by powering off associated circuitry thatperforms microphone signal processing. In some embodiments, samplingaudio ceases by not processing audio input received from the microphonethrough software recognition algorithms. Optionally, at block 1314, thedevice provides one or more of a haptic, audio, and visual outputindicating the end of the audio sampling.

It should be understood that the particular order in which theoperations in FIG. 13 has been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 1200 and 1500) are also applicable in an analogous manner tomethod 1300 described above with respect to FIG. 13 . For example, it ispossible for the device performing method 1300 to also perform method1500 (FIG. 15 ) for overcoming erroneous user cancellation of thevirtual assistant. For brevity, these details are not repeated here.

FIG. 14 is a flow diagram illustrating method 1400 of triggering avirtual assistant on an electronic device in accordance with someembodiments. Method 1400 is performed at one of devices 104, 200, 400,1000, and 1800 (FIGS. 1, 2, 4, 10, and 18 ) in some embodiments. In someembodiments, method 1400 is performed at a device having a touch screen.In some embodiments, method 1400 is performed at a device with aseparate display screen and a touch-sensitive surface. Operations inmethod 1400 are, optionally, combined and/or the order of someoperations is, optionally, changed.

At block 1402, the device detects user input via an input component ofthe device. At block 1404, the device determines if the input meets apredetermined condition. If the input meets a predetermined condition,processing proceeds to 1406 where the device samples audio inputreceived via its microphone. If the input does not meet thepredetermined condition, processing returns to block 1402, where thedevice optionally detects another user input.

In some embodiments, the predetermined condition is that the devicereceives the user input while its display is off. The device determineswhether the display is off, for example, by determining whether itsbacklight is lit.

In some embodiments, the predetermined condition is a movement of thedevice, such as a lifting of the device into a viewing position (e.g.,as seen in FIGS. 8A-8B and 10A-10B). In some embodiments, thepredetermined condition is based on an amount of lifting of theelectronic device during a time interval, the amount of liftingdetermined from an accelerometer of the electronic device. In someembodiments, the predetermined condition is based on smoothness of alifting of the electronic device during a time interval, the smoothnessof the lifting determined from an accelerometer of the electronicdevice. In some embodiments, the predetermined condition comprises aminimum period of dwell time in a position in accordance with thelifting of the electronic device.

In some embodiments, the predetermined condition is activation of aninput device such as a mechanical button, touch-sensitive button,rotatable input device, so forth. In some examples, the predeterminedcondition is a touch on touch-sensitive surface or touch screen.

Optionally, at block 1404, the device determines whether it is operatingin a predetermined mode where its audio output is muted (e.g., a “do notdisturb”). If the device is operating is such a mode, processing returnsto block 1402, meaning that the device foregoes sampling audio fortriggering a virtual assistant.

In some embodiments, sampling audio at block 1406 involves powering on amicrophone of the device. In some embodiments, sampling audio involvespowering on additional electronics circuitry to perform signalprocessing. In some embodiments, sampling audio involves passing audioinput received from the microphone to software recognition algorithmsthat are being executed on one or more processors of the device.

In some embodiments, the device proceeds from block 1402 (where theinput is detected) to block 1406 (where audio sampling occurs) withoutturning on its display (e.g., by not turning on the backlight of thedisplay). Optionally, the device provides at least one of a haptic andaudio output at block 1406 without powering on its display. In someembodiments, the device provides a visual output from a light sourceother than its display as it starts to sample audio input.

Having sampled audio input at block 1406, the device proceeds to block1408, where it determines whether sampled audio input comprises a spokentrigger for triggering a virtual assistant. If the sampled audio inputcontains the spoken trigger, processing proceeds to block 1410 where thedevice triggers a virtual assistant session. In some embodiments, thespoken trigger is a predetermined phrase, such as “hey Siri.”

In some embodiments, the device proceeds from block 1402 (where theinput is detected) to block 1408 (where the virtual assistant istriggered) while the display of the device remains off (e.g., by notturning on the backlight of the display). In some embodiments, thedevice provides at least one of a haptic and audio output as it triggersthe virtual assistant at block 1410. In some embodiments, the deviceprovides a visual output from a light source other than its display asit triggers the virtual assistant at block 1410.

If the sampled audio input does not contain the spoken trigger,processing proceeds to block 1412, where the device determines whetherto continue to sample audio input. If the device is to continue samplingaudio input, processing returns to block 1406 where audio samplingcontinues. If the device is to cease sampling of audio input, processingproceeds to block 1414 where audio sampling is stopped.

In some embodiments, the devices ceases to sample audio input aftersampling for a threshold duration of time, such as a duration of eightseconds. In some embodiments, the device ceases to sample audio afterdetecting activation of an input device such as a mechanical button,touch-sensitive button, rotatable input device, so forth. In someembodiments, the device ceases to sample audio after detectingactivation of an input device such as a touch on touch-sensitive surfaceor touch screen.

In some embodiments, the device ceases to sample audio input after anintervening input is received, such as a user input to invoke anotherapplication installed on the device. In some embodiments, the deviceceases to sample audio based on an amount of lowering of the deviceduring a time interval, the amount of lowering determined from anaccelerometer of the electronic device. In some embodiments, the deviceceases to sample audio based on smoothness of a lowering of theelectronic device during a time interval, the smoothness of the loweringdetermined from an accelerometer of the device. In some embodiments, thedevice ceases to sample audio input after identifying an audio endpointin the audio input. Exemplary end points include those indicating thatthe received audio input is too low in volume to be near-field speech(as opposed to background noise), unlikely to be human speech, a stop inthe user's spoken input, so forth.

In some embodiments, the device ceases sampling of audio ceases at block1414 by powering off the microphone of the device. In some embodiments,sampling of audio ceases by powering off associated circuitry thatperforms microphone signal processing. In some embodiments, samplingaudio ceases by not processing audio input received from the microphonethrough software recognition algorithms.

Optionally, the device provides at least one of a haptic and audiooutput as it ceases to sample audio input without turning on itsdisplay. In some embodiments, the device provides a visual output from alight source other than its display as it ceases to sample audio input.

It should be understood that the particular order in which theoperations in FIG. 14 has been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 1300 and 1500) are also applicable in an analogous manner tomethod 1400 described above with respect to FIG. 14 . For example, it ispossible for the device performing method 1400 to also perform method1500 (FIG. 15 ) for overcoming erroneous user cancellation of thevirtual assistant. For brevity, these details are not repeated here.

FIG. 15 is a flow diagram illustrating method 1500 of triggering avirtual assistant on an electronic device in accordance with someembodiments. Method 1500 is performed at one of devices 104, 200, 400,1100, and 1900 (FIGS. 1, 2, 11, and 19 ) in some embodiments. In someembodiments, method 1500 is performed at a device having a touch screen.In some embodiments, method 1500 is performed at a device with aseparate display screen and a touch-sensitive surface. Operations inmethod 1500 are, optionally, combined and/or the order of someoperations is, optionally, changed.

At block 1502, the electronic device samples audio input and determineswhether the audio input represents an executable task, for example, auser request that is provided in spoken natural language. While samplingaudio input, the device can provide a UI indicating of the sampling,such as screen 1106 of FIG. 11A.

In some embodiments, sampling of audio input occurs when the device'sdisplay is powered on, for example, when the backlight of the display islit. In some embodiments, the device samples audio input responsive to amovement meeting a predetermined condition, such as a lifting of thedevice into a viewing position (as seen in FIGS. 8A-8B, 10A-10B, and11A). In some embodiments, the predetermined condition is based on anamount of lifting of the electronic device during a time interval, theamount of lifting determined from an accelerometer of the electronicdevice. In some embodiments, the predetermined condition is based onsmoothness of a lifting of the electronic device during a time interval,the smoothness of the lifting determined from an accelerometer of theelectronic device. In some embodiments, the predetermined conditioncomprises a minimum period of dwell time in a position in accordancewith the lifting of the electronic device.

In some embodiments, the predetermined condition is activation of aninput device such as a mechanical button, touch-sensitive button,rotatable input device, so forth. In some embodiments, the predeterminedcondition is a touch on touch-sensitive surface or touch screen.

At block 1504, while sampling audio input, the electronic devicereceives an instruction to cease sampling of audio input. In someembodiments, the device is adapted to receive instruction to ceasesampling of audio input from a user of the device. The instruction canbe received as a spoken instruction via the microphone of the device,for example. Also, the instruction can be received by detectingactivation of an input device such as a touch on touch-sensitive surfaceor touch screen, such as a touch on affordance 1108 in FIG. 11A, forexample. Further, the instruction can be received by detectingactivation of a mechanical button, touch-sensitive button, rotatableinput device, so forth, for example.

In some embodiments, the device is adapted to receive instruction tocease sampling of audio input from another electronic device external tothe device. The instruction can be received through a communicationmedium such as cellular communication, Bluetooth communication, WiFicommunication, or the like.

In some embodiments, at block 1504, the device prompts the user forspoken input. In some embodiments, at block 1504, the device determineswhether the audio input represents a request, and in accordance withdetermining whether the audio input represents a task, the device:determines a user intent based on at least a portion of the audio input;identifies and executes the task based on the user intent; and providesat least one of a haptic, audio, and visual output representingexecution of the task.

At block 1506, responsive to the instruction to cease sampling of audioinput, the device provides an output acknowledgement. Theacknowledgement reports to the user that the virtual assistant has beencanceled, for example. In some embodiments, the acknowledgement involvesone or more of a haptic, audio, and visual output. In some embodiments,the acknowledgement involves turning the display off, as seen in FIG.11B.

In some embodiments, after receiving the instruction to cease samplingof audio input at block 1504 and after providing the acknowledgement atblock 1506, processing proceeds to block 1508, where the devicecontinues to sample audio input and determines whether the audio inputincludes a user task, for some limited time (after which the deviceceases to sample audio input).

In some embodiments, the device ceases to sample audio input after thedevice's display is turned off. In some embodiments, the devices ceasesto sample audio input after continuing to sample for a thresholdduration of time, such as a duration of eight seconds. In someembodiments, the device ceases to sample audio after detectingactivation of an input device such as a mechanical button,touch-sensitive button, rotatable input device, so forth. In someembodiments, the device ceases to sample audio after detectingactivation of an input device such as a touch on touch-sensitive surfaceor touch screen.

In some embodiments, the device ceases to sample audio input after anintervening input is received, such as a user input to invoke anotherapplication installed on the device. In some embodiments, the deviceceases to sample audio based on an amount of lowering of the deviceduring a time interval, the amount of lowering determined from anaccelerometer of the electronic device. In some embodiments, the deviceceases to sample audio based on smoothness of a lowering of theelectronic device during a time interval, the smoothness of the loweringdetermined from an accelerometer of the device. In some embodiments, thedevice ceases to sample audio input after identifying an audio endpointin the audio input. Exemplary end points include those indicating thatthe received audio input is too low in volume to be near-field speech(as opposed to background noise), unlikely to be human speech, a stop inthe user's spoken input, so forth.

In some embodiments, after receiving the instruction to cease samplingof audio input 1504, the device determines whether the instruction tocease sampling of audio input originates from a user or an externaldevice. In accordance with a determination that the audio inputoriginated from an external device, the device ceases to sample audioinput immediately.

In some embodiments, the device ceases sampling of audio ceases at block1506 by powering off the microphone of the device. In some embodiments,sampling of audio ceases by powering off associated circuitry thatperforms microphone signal processing. In some embodiments, samplingaudio ceases by not processing audio input received from the microphonethrough software recognition algorithms. Optionally, at block 1506, thedevice provides one or more of a haptic, audio, and visual outputindicating the end of the audio sampling.

It should be understood that the particular order in which theoperations in FIG. 15 has been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 1200, 1300, 1400, 2100) are also applicable in an analogousmanner to method 1500 described above with respect to FIG. 15 . Forexample, it is possible for the device performing method 1500 to alsoperform method 1400 for triggering virtual assistant sessions. Forbrevity, these details are not repeated here.

FIG. 21 is a flow diagram illustrating method 2100 of triggering avirtual assistant on an electronic device in accordance with someembodiments. Method 2100 is performed at one of devices 104, 200, 400,and 2000 (FIGS. 1, 2, 4, 8, and 20 ) in some embodiments. In someembodiments, method 2100 is performed at a device having a touch screen.In some embodiments, method 2100 is performed at a device with aseparate display screen and a touch-sensitive surface. Operations inmethod 1200 are, optionally, combined and/or the order of someoperations is, optionally, changed.

At block 2102, while a predetermined service such as a virtual assistantis executing on the device, the device detects a user's natural languageinput such as spoken input. At block 2104, the device operationalizesthe user's input by identifying one or more computing tasks to beperformed. At block 2106, while performing the one or more tasks, thedevice powers down its display screen (e.g., by turning off thebacklight of the screen). At block 2108, after completing the one ormore computing tasks, the device provides a haptic and/or audio output.

It should be understood that the particular order in which theoperations in FIG. 21 has been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 1200, 1300, 1400, and 1500) are also applicable in an analogousmanner to method 2100 described above with respect to FIG. 21 . Forexample, it is possible for the device performing method 2100 to alsoperform method 1400 for triggering virtual assistant sessions. Forbrevity, these details are not repeated here.

It is noted that the sampling of audio input at blocks 1206, 1306, 1406,and 1502 (FIGS. 12, 13, 14, and 15 ) can occur independent of whetherthe electronic device is being charged. However, such sampling of audioinput can depend on the remaining battery level of the device. In someexamples, a device optionally samples audio input consistent with theabove-described processes, but forego sampling of audio input when itsremaining battery level is below a threshold level.

In accordance with some embodiments, FIG. 16 shows a functional blockdiagram of an electronic device 1600 configured in accordance with theprinciples of the various described embodiments, including thosedescribed with reference to FIGS. 8 and 12 . The functional blocks ofthe device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 16 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 16 , an electronic device 1600 includes a display unit1602 configured to display a graphical user interface, optionaltouch-sensitive surface unit 1604 to receive contacts, a microphone unit1606 to detect audio input, optional movement sensor unit 1608 to obtainmovement readings such as acceleration in a time interval, optionalinput device unit 1610 such as a button, optional feedback unit 1612 toprovide feedback such as audio, haptic, and/or visual feedback, andprocessing unit 1614 coupled to the above-described units. In someembodiments, processing unit 1614 includes display enabling unit 1616,input detection unit 1618, audio sampling unit 1620, audio processingunit 1622, virtual assistant service unit 1624, and, optionally,feedback enabling unit 1626.

In some embodiments, processing unit 1614 is configured to: while thedisplay is on, receive (e.g., with display enabling unit 1616) userinput via the input device, the user input meeting a predeterminedcondition; in accordance with receiving the user input meeting thepredetermined condition (e.g., with input detection unit 1618), sampleaudio input (e.g., with audio sampling unit 1620) received via themicrophone (e.g., from microphone unit 1606); determine whether theaudio input comprises a spoken trigger (e.g., with audio processing unit1622); and in accordance with a determination that audio input comprisesthe spoken trigger (e.g., with audio processing unit 1622), trigger avirtual assistant session (e.g., with virtual assistant service unit1624).

In some embodiments, the predetermined condition is based on an amountof lifting of the electronic device during a time interval, the amountof lifting determined from an accelerometer of the electronic device(e.g., movement sensor unit 1608). In some embodiments, thepredetermined condition is based on smoothness of a lifting of theelectronic device during a time interval, the smoothness of the liftingdetermined from an accelerometer of the electronic device (e.g.,movement sensor unit 1608). In some embodiments, the predeterminedcondition comprises a minimum period of dwell time in a position inaccordance with the lifting of the electronic device. In someembodiments, the predetermined condition comprises detecting (e.g.,input detection unit 1618) activation of a button of the electronicdevice (e.g., input device unit 1610).

In some embodiments, the predetermined condition comprises detectingtouch input on a touch-sensitive surface of the electronic device (e.g.,touch-sensitive surface unit 1604).

In some embodiments, the processing unit is further configured to:determine (e.g., with display enabling unit 1616) whether the display ison; the sampling of audio input (e.g., with audio sampling unit 1620)occurs in accordance with a determination that the display is on. Insome embodiments, the processing unit is further configured to: inaccordance with determining whether the display is on, determine whetherthe backlight of the display is on (e.g., with display enabling unit1616).

In some embodiments, the processing unit is further configured to: ceasethe sampling of audio input after the sampling of audio input hasoccurred for a predetermined duration of time (e.g., with audio samplingunit 1620).

In some embodiments, the user input meeting a predetermined condition isa first user input meeting a first predetermined condition, andprocessing unit 1614 is further configured to: while sampling audioinput (e.g., with audio sampling unit 1620) in accordance with receivingthe first user input, receiving a second user input (e.g., with inputdetection unit 1618) meeting a second predetermined condition; and inaccordance with receiving the second user input meeting the secondpredetermined condition, ceasing (e.g., with audio sampling unit 1620)the sampling of audio input.

In some embodiments, the second predetermined condition is based on anamount of lowering of the electronic device during a time interval, theamount of lowering determined from an accelerometer of the electronicdevice (e.g., with movement sensor unit 1608).

In some embodiments, the first predetermined condition is based onsmoothness of a lowering of the electronic device during a timeinterval, the smoothness of the lowering determined from anaccelerometer of the electronic device (e.g., with movement sensor unit1608).

In some embodiments, the second predetermined condition comprisesdetecting (e.g., with input detection unit 1618) activation of a buttonof the electronic device. In some embodiments, the second predeterminedcondition comprises detecting touch input on a touch-sensitive surfaceof the electronic device.

In some embodiments, processing unit 1614 is further configured to:while sampling audio input in accordance with receiving the user inputmeeting the predetermined condition (e.g., with audio sampling unit1620), determining whether the display is off (e.g., with displayenabling unit 1616); and in accordance with a determination that thedisplay is off, ceasing (e.g., with audio sampling unit 1620) thesampling of audio input.

In some embodiments, processing unit 1614 is further configured to:while sampling audio input in accordance with receiving the user inputmeeting the predetermined condition (e.g., with audio sampling unit1620), identifying an audio endpoint in the audio input (e.g., withaudio processing unit 1622); and in response to identifying the audioendpoint, ceasing (e.g., with audio sampling unit 1620) the sampling ofaudio input.

In some embodiments, processing unit 1614 is further configured to: inaccordance with ceasing to sample audio input, causing a haptic output(e.g., with feedback enabling unit 1626 and/or feedback unit 1612).

In some embodiments, processing unit 1614 is further configured to: inaccordance with triggering the virtual assistant session (e.g., withvirtual assistant service unit 1624), prompting (e.g., with displayenabling unit 1616 and/or feedback enabling unit 1626) a user for spokeninput (e.g., with display unit 1602 and/or feedback unit 1612).

In some embodiments, the audio input comprises the spoken trigger andadditional input, and processing unit 1614 is further configured to, inaccordance with triggering the virtual assistant session: determining auser intent based on at least the additional input in the audio input,and executing a task associated with the user intent (e.g., with virtualassistant service unit 1624).

In some embodiments, processing unit 1614 is further configured to: inaccordance with a determination that the electronic device is operatingin a predetermined mode (e.g., with virtual assistant service unit1624), forgoing sampling of audio input (e.g., with audio sampling unit1620), even after receiving the user input meeting the predeterminedcondition while the display is on.

In some embodiments, operation in the predetermined mode comprisesmuting audio output of the electronic device. In some embodiments, thespoken trigger comprises comprise a predetermined phrase.

The operations described above with respect to FIG. 12 , optionally,implemented by components depicted in FIGS. 1, 2, 7A-7B, or FIG. 16 .For example, sampling audio operation 1202 is optionally implemented byaudio circuitry 210 (FIG. 2 ). When audio having a spoken trigger isdetected, the device uses display controller 256 (FIG. 2 ) and/or hapticfeedback controller 261 (FIG. 2 ) to provide corresponding output. Itwould be clear to a person of ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1, 2, 7A-7B, or FIG. 16 .

It is understood by persons of skill in the art that the functionalblocks described in FIG. 16 are, optionally, combined or separated intosub-blocks to implement the principles of the various describedembodiments. Therefore, the description herein optionally supports anypossible combination or separation or further definition of thefunctional blocks described herein. For example, units 1602-1612 canhave associated “controller” units that are operatively coupled with therespective unit and processing unit 1614 to enable operation. Thesecontroller units are not separately illustrated in FIG. 16 but areunderstood to be within the grasp of one of ordinary skill in the artwho is designing a device having units 1602-1612 such as device 1600.The description herein thus optionally supports combination, separation,and/or further definition of the functional blocks described herein.

In accordance with some embodiments, FIG. 17 shows a functional blockdiagram of an electronic device 1700 configured in accordance with theprinciples of the various described embodiments, including thosedescribed with reference to FIGS. 9 and 13 . The functional blocks ofthe device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 17 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 17 , an electronic device 1700 includes a display unit1702 configured to display a graphical user interface, optionaltouch-sensitive surface unit 1704 to receive contacts, a microphone unit1706 to detect audio input, optional movement sensor unit 1708 to obtainmovement readings such as acceleration in a time interval, optionalinput device unit 1710 such as a button, optional feedback unit 1712 toprovide feedback such as audio, haptic, and/or visual feedback, andprocessing unit 1714 coupled to the above-described units. In someembodiments, processing unit 1714 includes display enabling unit 1716,software event detection input 1728, input detection unit 1718, audiosampling unit 1720, audio processing unit 1722, virtual assistantservice unit 1724, and, optionally, feedback enabling unit JJ26.

In some embodiments, processing unit 1714 is configured to: detect asoftware event (e.g., with software event detection unit 1728) meeting apredetermined condition; in accordance with a determination that thesoftware event meeting the condition is detected, sample audio input(e.g., with audio sampling unit 1620) received via the microphone (e.g.,microphone unit 1706); determine (e.g., with audio processing unit 1722)whether audio input received via the microphone comprises a spokentrigger; and in accordance with a determination that the audio inputcomprises the spoken trigger, trigger a virtual assistant session (e.g.,with virtual assistant service unit 1724).

In some embodiments, the predetermined condition is that the softwareevent is an event triggered by an application of the electronic device.In some embodiments, the predetermined condition comprises the softwareevent representing a notification. In some embodiments, thepredetermined condition comprises the software event representing acalendar notification.

In some embodiments, the predetermined condition comprises the softwareevent representing an incoming calendar invitation from an externaldevice. In some embodiments, the predetermined condition comprises thesoftware event representing an incoming transmission, the transmissiontriggered from an external device. In some embodiments, thepredetermined condition comprises the software event representing anincoming phone call from an external device. In some embodiments, thepredetermined condition comprises the software event representing anincoming text or multimedia message from an external device.

In some embodiments, processing unit 1714 is further configured to: inaccordance with triggering a virtual assistant session, initiating(e.g., with virtual assistant service unit 1624) a response addressed tothe external device. An exemplary response is a reply to an incomingmessage, such as text message 916 in FIG. 9C. Other exemplary responsesinclude e-mail messages, multi-media messages, calendar invitationresponses, so forth. As used herein, initiation In the example of FIG.9C, responsive text message 916 was transmitted by device 900automatically based on user instructions 910. Optionally, afterinitiating message 916 (e.g., populating the message with recipientinformation and content), the device can prompt the user for a finalconfirmation before sending the message to the recipient.

In some embodiments, processing unit 1714 is further configured to:determining (e.g., with display enabling unit 1716) whether the displayis on, and wherein the sampling of audio input (e.g., with audiosampling unit 1720) occurs in accordance with a determination that thedisplay is on.

In some embodiments, processing unit 1714 is further configured to: inaccordance with determining whether the display is on (e.g., withdisplay enabling unit 1716), determining (e.g., with display enablingunit 1716) whether the backlight of the display is on.

In some embodiments, processing unit 1714 is further configured to:cease the sampling of audio input (e.g., with audio sampling unit 1720)after the sampling of audio input has occurred for a predeterminedduration of time.

In some embodiments, the user input meeting a predetermined condition isa first user input meeting a first predetermined condition, andprocessing unit 1714 is further configured to: while sampling audioinput (e.g., with audio sampling unit 1720) in accordance with receivingthe first user input, receiving (e.g., with input detection unit 1718) asecond user input meeting a second predetermined condition; and inaccordance with receiving the second user input meeting the secondpredetermined condition, ceasing (e.g., with audio sampling unit 1720)the sampling of audio input.

In some embodiments, the second predetermined condition is based on anamount of lowering of the electronic device during a time interval, theamount of lowering determined from an accelerometer (e.g., with movementsensor unit 1708) of the electronic device. In some embodiments, thefirst predetermined condition is based on smoothness of a lowering ofthe electronic device during a time interval, the smoothness of thelowering determined from an accelerometer (e.g., with movement sensorunit 1708) of the electronic device.

In some embodiments, the second predetermined condition comprisesdetecting activation (e.g., with input detection unit 1718) of a button(e.g., with input device unit 1710) of the electronic device. In someembodiments, the second predetermined condition comprises detectingtouch input on a touch-sensitive surface (e.g., with touch-sensitivesurface unit 1704) of the electronic device.

In some embodiments, processing unit 1714 is further configured to:while sampling audio input (e.g., with audio sampling unit 1720) inaccordance with receiving the user input meeting the predeterminedcondition, determining (e.g., with display enabling unit 1716) whetherthe display is off; and in accordance with a determination that thedisplay is off, ceasing the sampling of audio input (e.g., with audiosampling unit 1720).

In some embodiments, processing unit 1714 is further configured to:while sampling audio input (e.g., with audio sampling unit 1720) inaccordance with receiving the user input meeting the predeterminedcondition, identifying (e.g., with audio processing unit 1722) an audioendpoint in the audio input; and in response to identifying the audioendpoint, ceasing the sampling of audio input (e.g., with audio samplingunit 1720).

In some embodiments, processing unit 1714 is in accordance with ceasingto sample audio input, causing (e.g., with feedback enabling unit 1726)a haptic output (e.g., with feedback unit 1712).

In some embodiments, processing unit 1714 is in accordance withtriggering the virtual assistant session, prompting (e.g., with displayenabling unit 1716 and/or feedback enabling unit 1726) a user for spokeninput (e.g., with display unit 1702 and/or feedback unit 1712).

In some embodiments, the audio input comprises the spoken trigger andadditional input, and processing unit 1714 is further configured to: inaccordance with triggering the virtual assistant session (e.g., withvirtual assistant service unit 1724): determining (e.g., with virtualassistant service unit 1724) a user intent based on at least theadditional input in the audio input, and executing (e.g., with virtualassistant service unit 1724) a task associated with the user intent.

In some embodiments, processing unit 1714 is further configured to: inaccordance with a determination that the electronic device is operatingin a predetermined mode (e.g., with virtual assistant service unit1724), forgoing sampling of audio input (e.g., with audio sampling unit1720), even after receiving (e.g., with input detection unit 1718) userinput meeting the predetermined condition while the display is on.

In some embodiments, operation in the predetermined mode comprisesmuting audio output of the electronic device. In some embodiments, thespoken trigger comprises comprise a predetermined phrase, such as “heySiri.”

The operations described above with respect to FIG. 13 , optionally,implemented by components depicted in FIGS. 1, 2, 7A-7B, or FIG. 17 .For example, sampling audio operation 1202 is optionally implemented byaudio circuitry 210 (FIG. 2 ). When audio having a spoken trigger isdetected, the device uses display controller 256 (FIG. 2 ) and/or hapticfeedback controller 261 (FIG. 2 ) to provide corresponding output. Itwould be clear to a person of ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1, 2, 7A-7B, or FIG. 17 .

It is understood by persons of skill in the art that the functionalblocks described in FIG. 17 are, optionally, combined or separated intosub-blocks to implement the principles of the various describedembodiments. Therefore, the description herein optionally supports anypossible combination or separation or further definition of thefunctional blocks described herein. For example, units 1702-1712 canhave associated “controller” units that are operatively coupled with therespective unit and processing unit 1714 to enable operation. Thesecontroller units are not separately illustrated in FIG. 17 but areunderstood to be within the grasp of one of ordinary skill in the artwho is designing a device having units 1702-1712 such as device 1700.The description herein thus optionally supports combination, separation,and/or further definition of the functional blocks described herein.

In accordance with some embodiments, FIG. 18 shows a functional blockdiagram of an electronic device 1800 configured in accordance with theprinciples of the various described embodiments, including thosedescribed with reference to FIGS. 10 and 14 . The functional blocks ofthe device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 18 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 18 , an electronic device 1800 includes a display unit1802 configured to display a graphical user interface, optionaltouch-sensitive surface unit 1804 to receive contacts, a microphone unit1806 to detect audio input, optional movement sensor unit 1808 to obtainmovement readings such as acceleration in a time interval, optionalinput device unit 1810 such as a button, optional feedback unit 1812 toprovide feedback such as audio, haptic, and/or visual feedback, andprocessing unit 1814 coupled to the above-described units. In someembodiments, processing unit 1814 includes display enabling unit 1816,input detection unit 1818, audio sampling unit 1820, audio processingunit 1822, virtual assistant service unit 1824, and, optionally,feedback enabling unit 1826.

In some embodiments, processing unit 1814 is configured to: receive(e.g., with input detection unit 1818) user input via the input device,the user input meeting a predetermined condition; in accordance withreceiving the user input meeting the predetermined condition, samplingaudio input (e.g., with audio sampling unit 1820) received via themicrophone; determining (e.g., with audio processing unit 1822) whetherthe audio input comprises a spoken trigger; in accordance with adetermination that audio input comprises the spoken trigger: triggering(e.g., with virtual assistant service unit 1824) a virtual assistantsession and causing a haptic output (e.g., with feedback unit 1826).

In some embodiments, processing unit 1814 is further configured to: inaccordance with receiving the user input meeting a predeterminedcondition, receiving the user input (e.g., with input detection unit1818) while the display is off.

In some embodiments, processing unit 1814 is further configured toe: inaccordance with triggering the virtual assistant session, triggering thevirtual assistant session (e.g., with virtual assistant service unit1824) without turning on a backlight of the display

In some embodiments, the predetermined condition is based on an amountof lifting of the electronic device during a time interval, the amountof lifting determined from an accelerometer of the electronic device(e.g., with movement unit 1808). In some embodiments, the predeterminedcondition is based on smoothness of a lifting of the electronic deviceduring a time interval, the smoothness of the lifting determined from anaccelerometer of the electronic device (e.g., with movement unit 1808).In some embodiments, the predetermined condition comprises a minimumperiod of dwell time in a position in accordance with the lifting of theelectronic device.

In some embodiments, the predetermined condition comprises detectingactivation of a button of the electronic device (e.g., with inputdetection unit 1818). In some embodiments, the predetermined conditioncomprises detecting touch input on a touch-sensitive surface of theelectronic device.

In some embodiments, processing unit 1814 is further configured to,ceasing the sampling of audio input (e.g., with audio sampling unit1820) after the sampling of audio input has occurred for a predeterminedduration of time.

In some embodiments, the user input meeting a predetermined condition isa first user input meeting a first predetermined condition, andprocessing unit 1814 is further configured to: while sampling audioinput (e.g., with audio sampling unit 1820) in accordance with receivingthe first user input, receiving a second user input (e.g., with inputdetection unit 1818) meeting a second predetermined condition; and inaccordance with receiving the second user input meeting the secondpredetermined condition, ceasing the sampling of audio input (e.g., withaudio sampling unit 1820).

In some embodiments, the second predetermined condition is based on anamount of lowering of the electronic device during a time interval, theamount of lowering determined from an accelerometer (e.g., with movementunit 1808) of the electronic device. In some embodiments, the firstpredetermined condition is based on smoothness of a lowering of theelectronic device during a time interval, the smoothness of the loweringdetermined from an accelerometer (e.g., with movement unit 1808) of theelectronic device.

In some embodiments, the second predetermined condition comprisesdetecting (e.g., with input detection unit 1818) activation of a button(e.g., with input device unit 1810) of the electronic device. In someembodiments, the second predetermined condition comprises detecting(e.g., with input detection unit 1818) touch input on a touch-sensitivesurface (e.g., with touch-sensitive surface unit 1804) of the electronicdevice.

In some embodiments, processing unit 1814 is further configured to,while sampling audio input (e.g., with audio sampling unit 1820) inaccordance with receiving the user input meeting the predeterminedcondition, identifying (e.g., with audio processing unit 1822) an audioendpoint in the audio input; and in response to identifying the audioendpoint, ceasing the sampling of audio input (e.g., with audio samplingunit 1820).

In some embodiments, processing unit 1814 is further configured to, inaccordance with ceasing to sample audio input (e.g., with audio samplingunit 1820), providing a causing output (e.g., with feedback unit 1826).In some embodiments, processing unit 1814 is further configured to, inaccordance with triggering the virtual assistant session (e.g., withvirtual assistant service unit 1824), prompting (e.g., with displayenabling unit 1816 and/or feedback enabling unit 1826) a user for spokeninput (e.g., with display unit 1802 and/or feedback unit 1812).

In some embodiments, the audio input comprises the spoken trigger andadditional input, and processing unit 1814 is further configured to: inaccordance with triggering the virtual assistant session (e.g., withvirtual assistant service unit 1824): determining (e.g., with virtualassistant service unit 1824) a user intent based on at least theadditional input in the audio input, and executing a task associatedwith the user intent (e.g., with virtual assistant service unit 1824).

In some embodiments, processing unit 1814 is further configured to, inaccordance with a determination that the electronic device is operatingin a predetermined mode, forgoing sampling of audio input (e.g., withaudio sampling unit 1820), even after receiving (e.g., with inputdetection unit 1818) the user input (e.g., with touch-sensitive surfaceunit 1804 or input device unit 1810) meeting the predetermined conditionwhile the display is on.

In some embodiments, operation in the predetermined mode comprisesmuting audio output of the electronic device. In some embodiments, thespoken trigger comprises comprise a predetermined phrase, such as “heySiri.”

The operations described above with respect to FIG. 14 , optionally,implemented by components depicted in FIGS. 1, 2, 7A-7B, or FIG. 18 .For example, sampling audio operation 1202 is optionally implemented byaudio circuitry 210 (FIG. 2 ). When audio having a spoken trigger isdetected, the device uses display controller 256 (FIG. 2 ) and/or hapticfeedback controller 261 (FIG. 2 ) to provide corresponding output. Itwould be clear to a person of ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1, 2, 7A-7B, or FIG. 18 .

It is understood by persons of skill in the art that the functionalblocks described in FIG. 19 are, optionally, combined or separated intosub-blocks to implement the principles of the various describedembodiments. Therefore, the description herein optionally supports anypossible combination or separation or further definition of thefunctional blocks described herein. For example, units 1802-1812 canhave associated “controller” units that are operatively coupled with therespective unit and processing unit 1814 to enable operation. Thesecontroller units are not separately illustrated in FIG. 18 but areunderstood to be within the grasp of one of ordinary skill in the artwho is designing a device having units 1802-1812 such as device 1800.The description herein thus optionally supports combination, separation,and/or further definition of the functional blocks described herein.

In accordance with some embodiments, FIG. 19 shows a functional blockdiagram of an electronic device 1900 configured in accordance with theprinciples of the various described embodiments, including thosedescribed with reference to FIGS. 8 and 12 . The functional blocks ofthe device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 19 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 19 , an electronic device 1900 includes a display unit1902 configured to display a graphical user interface, optionaltouch-sensitive surface unit 1904 to receive contacts, a microphone unit1906 to detect audio input, optional movement sensor unit 1908 to obtainmovement readings such as acceleration in a time interval, optionalinput device unit 1910 such as a button, optional feedback unit 1912 tocause feedback such as audio, haptic, and/or visual feedback, andprocessing unit 1914 coupled to the above-described units. In someembodiments, processing unit 1914 includes display enabling unit 1916,input detection unit 1918, audio sampling unit 1920, audio processingunit 1922, virtual assistant service unit 1924, and, optionally,feedback enabling unit 1926.

In some embodiments, processing unit 1914 is configured to: sample(e.g., with audio sampling unit 1920) audio input received via themicrophone and determine (e.g., with audio processing unit 1922) whetherthe audio input represents a task; while sampling audio input (e.g.,with audio sampling unit 1920), receive (e.g., with input detection unit1918) instruction to cease sampling of audio input; provide (e.g., withfeedback unit 1926) output acknowledging the received instruction tocease the sampling of audio input; and after providing the output,continue to sample audio input (e.g., with audio sampling unit 1920) anddetermine (e.g., with audio processing unit 1922) whether the audioinput comprises a task, for a duration, then cease the sampling of audioinput (e.g., with audio sampling unit 1920).

In some embodiments, processing unit 1914 is further configured to, inaccordance with sampling audio input (e.g., with audio sampling unit1920), sample (e.g., with audio sampling unit 1920) audio input whilethe display is on.

In some embodiments, processing unit 1914 is further configured to, inaccordance with providing (e.g., with feedback unit 1926) the outputacknowledging the received instruction to end the sampling of audioinput, cause (e.g., with feedback unit 1926) a haptic output (e.g., withfeedback unit 1912).

In some embodiments, processing unit 1914 is further configured to, inaccordance with providing (e.g., with feedback unit 1926) the outputacknowledging the received instruction to end the sampling of audioinput, provide (e.g., with feedback unit 1926) an audio output (e.g.,with feedback unit 1912).

In some embodiments, processing unit 1914 is further configured to, inaccordance with the sampling (e.g., with audio sampling unit 1920) ofaudio received via the microphone, prompt a user for spoken input (e.g.,with display enabling unit 1916 and display unit 1902, and/or withfeedback enabling unit 1926 and feedback unit 1912).

In some embodiments, processing unit 1914 is further configured to, inaccordance with determining (e.g., with virtual assistant service unit1924) whether the audio input represents a task, determine (e.g., withvirtual assistant service unit 1924) a user intent based on at least aportion of the audio input; identify and execute the task based on theuser intent (e.g., with virtual assistant service unit 1924); and cause(e.g., with feedback unit 1926) haptic output (e.g., with feedback unit1912) representing execution of the task.

In some embodiments, processing unit 1914 is further configured to,determine (e.g., with input detection unit 1918) whether the receivedinstruction to cease sampling of audio input is received from a user viathe electronic device or is received from an external device; where thecontinued sampling of audio input (e.g., with audio sampling unit 1920)and determining (e.g., with audio processing unit 1922) of whether theaudio input comprises a task for a duration after receiving theinstruction to cease sampling occurs in accordance with a determinationthat the received instruction is received from a user via the electronicdevice; and in accordance with a determination that the receivedinstruction is received from an external device, the device ceases thesampling of audio input (e.g., with audio sampling unit 1920) responsiveto the received instruction.

In some embodiments, the spoken trigger comprises comprise apredetermined phrase, such as “hey Siri.”

The operations described above with respect to FIG. 15 , optionally,implemented by components depicted in FIGS. 1, 2, 7A-7B, or FIG. 19 .For example, sampling audio operation 1202 is optionally implemented byaudio circuitry 210 (FIG. 2 ). When audio having a spoken trigger isdetected, the device uses display controller 256 (FIG. 2 ) and/or hapticfeedback controller 261 (FIG. 2 ) to provide corresponding output. Itwould be clear to a person of ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1, 2, 7A-7B, or FIG. 19 .

It is understood by persons of skill in the art that the functionalblocks described in FIG. 19 are, optionally, combined or separated intosub-blocks to implement the principles of the various describedembodiments. Therefore, the description herein optionally supports anypossible combination or separation or further definition of thefunctional blocks described herein. For example, units 1902-1912 canhave associated “controller” units that are operatively coupled with therespective unit and processing unit 1914 to enable operation. Thesecontroller units are not separately illustrated in FIG. 19 but areunderstood to be within the grasp of one of ordinary skill in the artwho is designing a device having units 1902-1912 such as device 1900.The description herein thus optionally supports combination, separation,and/or further definition of the functional blocks described herein.

Although the disclosure and examples have been fully described withreference to the accompanying figures, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe appended claims.

What is claimed is:
 1. An electronic device comprising: one or more processors; a memory; a microphone; and one or more programs, wherein the one or more programs are stored in memory and configured to be executed by the one or more processors, the one or more programs including instructions for: detecting a software event meeting a predetermined condition; in accordance with a determination that the software event meeting the predetermined condition is detected: detecting a signal associated with a user lifting the electronic device; and in accordance with a determination that an amount of lifting during a time interval exceeds a second predetermined condition: powering on the microphone; while powering on the microphone, providing an audio output; and after powering on the microphone, sampling audio input received via the microphone.
 2. The electronic device of claim 1, wherein the one or more programs further include instructions for: determining whether the audio input includes a spoken trigger; and in accordance with a determination that the audio input includes the spoken trigger, triggering a virtual assistant session.
 3. The electronic device of claim 2, the one or more programs further including instructions for: in accordance with triggering a virtual assistant session, initiating a response addressed to an external device.
 4. The electronic device of claim 2, wherein the audio input comprises the spoken trigger and additional input, the one or more programs further including instructions for: in accordance with triggering the virtual assistant session: determining a user intent based on at least the additional input in the audio input; and executing a task associated with the user intent.
 5. The electronic device of claim 2, wherein the spoken trigger comprises a predetermined phrase.
 6. The electronic device of claim 1, wherein the predetermined condition includes an event triggered by an application of the electronic device.
 7. The electronic device of claim 1, wherein the predetermined condition comprises an event representing a notification.
 8. The electronic device of claim 1, wherein the predetermined condition comprises an event representing an incoming calendar invitation from an external device.
 9. The electronic device of claim 1, wherein the predetermined condition comprises an event representing an incoming transmission, the transmission triggered from an external device.
 10. The electronic device of claim 9, wherein the incoming transmission includes an incoming phone call from the external device.
 11. The electronic device of claim 9, wherein the incoming transmission includes an incoming text or multimedia message from the external device.
 12. The electronic device of claim 1, the one or more programs further including instructions for: determining whether a display of the electronic device is on, and wherein the sampling of audio input occurs in accordance with a determination that the display is on.
 13. The electronic device of claim 1, the one or more programs further including instructions for: ceasing the sampling of audio input after the sampling of audio input has occurred for a predetermined duration of time.
 14. The electronic device of claim 1, the one or more programs further including instructions for: while sampling audio input receiving a user input meeting a third predetermined condition; and in accordance with receiving the user input meeting the third predetermined condition, ceasing the sampling of audio input.
 15. The electronic device of claim 14, wherein the third predetermined condition comprises detecting activation of a button of the electronic device.
 16. The electronic device of claim 14, wherein the third predetermined condition comprises detecting touch input on a touch-sensitive surface of the electronic device.
 17. The electronic device of claim 1, the one or more programs further including instructions for: while sampling the audio input, determining whether a display of the electronic device is off; and in accordance with a determination that the display is off, ceasing the sampling of audio input.
 18. The electronic device of claim 1, the one or more programs further including instructions for: while sampling the audio input, identifying an audio endpoint in the audio input; and in response to identifying the audio endpoint, ceasing the sampling of audio input.
 19. The electronic device of claim 1, the one or more programs further including instructions for: in accordance with a determination that the electronic device is operating in a predetermined mode, forgoing sampling of audio input, wherein operating in the predetermined mode comprises muting audio output of the electronic device.
 20. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by an electronic device with a display and a microphone, cause the electronic device to: detect a software event meeting a predetermined condition; in accordance with a determination that the software event meeting the predetermined condition is detected: detect a signal associated with a user lifting the electronic device; and in accordance with a determination that an amount of lifting during a time interval exceeds a second predetermined condition: power on the microphone; while powering on the microphone, provide an audio output; and after powering on the microphone, sample audio input received via the microphone.
 21. The non-transitory computer readable storage medium of claim 20, the one or more programs further comprising instructions, which when executed by an electronic device with a display and a microphone, cause the electronic device to: determine whether the audio input includes a spoken trigger; and in accordance with a determination that the audio input includes the spoken trigger, trigger a virtual assistant session.
 22. The non-transitory computer readable storage medium of claim 21, the one or more programs further comprising instructions, which when executed by an electronic device with a display and a microphone, cause the electronic device to: in accordance with triggering a virtual assistant session, initiate a response addressed to an external device.
 23. The non-transitory computer readable storage medium of claim 21, the one or more programs further comprising instructions, which when executed by an electronic device with a display and a microphone, cause the electronic device to: in accordance with triggering the virtual assistant session: determine a user intent based on at least the additional input in the audio input; and execute a task associated with the user intent.
 24. The non-transitory computer readable storage medium of claim 21, wherein the spoken trigger comprises a predetermined phrase.
 25. The non-transitory computer readable storage medium of claim 20, wherein the predetermined condition includes an event triggered by an application of the electronic device.
 26. The non-transitory computer readable storage medium of claim 20, wherein the predetermined condition comprises an event representing a notification.
 27. The non-transitory computer readable storage medium of claim 20, wherein the predetermined condition comprises an event representing an incoming calendar invitation from an external device.
 28. The non-transitory computer readable storage medium of claim 20, wherein the predetermined condition comprises an event representing an incoming transmission, the transmission triggered from an external device.
 29. The non-transitory computer readable storage medium of claim 28, wherein the incoming transmission includes an incoming phone call from the external device.
 30. The non-transitory computer readable storage medium of claim 28, wherein the incoming transmission includes an incoming text or multimedia message from the external device.
 31. The non-transitory computer readable storage medium of claim 20, the one or more programs further comprising instructions, which when executed by an electronic device with a display and a microphone, cause the electronic device to: determine whether a display of the electronic device is on, and wherein the sampling of audio input occurs in accordance with a determination that the display is on.
 32. The non-transitory computer readable storage medium of claim 20, the one or more programs further comprising instructions, which when executed by an electronic device with a display and a microphone, cause the electronic device to: cease the sampling of audio input after the sampling of audio input has occurred for a predetermined duration of time.
 33. The non-transitory computer readable storage medium of claim 20, the one or more programs further comprising instructions, which when executed by an electronic device with a display and a microphone, cause the electronic device to: while sampling audio input, receive a user input meeting a third predetermined condition; and in accordance with receiving the user input meeting the third predetermined condition, cease the sampling of audio input.
 34. The non-transitory computer readable storage medium of claim 33, wherein the third predetermined condition comprises detecting activation of a button of the electronic device.
 35. The non-transitory computer readable storage medium of claim 33, wherein the third predetermined condition comprises detecting touch input on a touch-sensitive surface of the electronic device.
 36. The non-transitory computer readable storage medium of claim 20, the one or more programs further comprising instructions, which when executed by an electronic device with a display and a microphone, cause the electronic device to: while sampling the audio input, determine whether a display of the electronic device is off; and in accordance with a determination that the display is off, cease the sampling of audio input.
 37. The non-transitory computer readable storage medium of claim 20, the one or more programs further comprising instructions, which when executed by an electronic device with a display and a microphone, cause the electronic device to: while sampling the audio input, identify an audio endpoint in the audio input; and in response to identifying the audio endpoint, cease the sampling of audio input.
 38. The non-transitory computer readable storage medium of claim 20, the one or more programs further comprising instructions, which when executed by an electronic device with a display and a microphone, cause the electronic device to: in accordance with a determination that the electronic device is operating in a predetermined mode, forgo sampling of audio input, wherein operating in the predetermined mode comprises muting audio output of the electronic device.
 39. A method, comprising: at an electronic device with a display and a microphone: detecting a software event meeting a predetermined condition; in accordance with a determination that the software event meeting the predetermined condition is detected: detecting a signal associated with a user lifting the electronic device; and in accordance with a determination that an amount of lifting during a time interval exceeds a second predetermined condition: powering on the microphone; while powering on the microphone, providing an audio output; and after powering on the microphone, sampling audio input received via the microphone.
 40. The method of claim 39, further comprising: determining whether the audio input includes a spoken trigger; and in accordance with a determination that the audio input includes the spoken trigger, triggering a virtual assistant session.
 41. The method of claim 40, further comprising: in accordance with triggering a virtual assistant session, initiating a response addressed to an external device.
 42. The method of claim 40, further comprising: in accordance with triggering the virtual assistant session: determining a user intent based on at least the additional input in the audio input; and executing a task associated with the user intent.
 43. The method of claim 40, wherein the spoken trigger comprises a predetermined phrase.
 44. The method of claim 39, wherein the predetermined condition includes an event triggered by an application of the electronic device.
 45. The method of claim 39, wherein the predetermined condition comprises an event representing a notification.
 46. The method of claim 39, wherein the predetermined condition comprises an event representing an incoming calendar invitation from an external device.
 47. The method of claim 39, wherein the predetermined condition comprises an event representing an incoming transmission, the transmission triggered from an external device.
 48. The method of claim 47, wherein the incoming transmission includes an incoming phone call from the external device.
 49. The method of claim 47, wherein the incoming transmission includes an incoming text or multimedia message from the external device.
 50. The method of claim 39, further comprising: determining whether a display of the electronic device is on, and wherein the sampling of audio input occurs in accordance with a determination that the display is on.
 51. The method of claim 39, further comprising: ceasing the sampling of audio input after the sampling of audio input has occurred for a predetermined duration of time.
 52. The method of claim 39, further comprising: while sampling audio input, receiving a user input meeting a third predetermined condition; and in accordance with receiving the user input meeting the third predetermined condition, ceasing the sampling of audio input.
 53. The method of claim 52, wherein the third predetermined condition comprises detecting activation of a button of the electronic device.
 54. The method of claim 52, wherein the third predetermined condition comprises detecting touch input on a touch-sensitive surface of the electronic device.
 55. The method of claim 39, further comprising: while sampling the audio input, determining whether a display of the electronic device is off; and in accordance with a determination that the display is off, ceasing the sampling of audio input.
 56. The method of claim 39, further comprising: while sampling the audio input, identifying an audio endpoint in the audio input; and in response to identifying the audio endpoint, ceasing the sampling of audio input.
 57. The method of claim 39, further comprising: in accordance with a determination that the electronic device is operating in a predetermined mode, forgoing sampling of audio input, wherein operating in the predetermined mode comprises muting audio output of the electronic device. 